New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SofaExporter] Move bindings from SofaPython #1095
[SofaExporter] Move bindings from SofaPython #1095
Conversation
[ci-build][with-all-tests] |
@@ -188,6 +187,7 @@ endif() | |||
target_include_directories(${PROJECT_NAME} PUBLIC "$<BUILD_INTERFACE:${CMAKE_BINARY_DIR}/include>") | |||
target_include_directories(${PROJECT_NAME} PUBLIC "$<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/..>") | |||
target_include_directories(${PROJECT_NAME} PUBLIC "$<INSTALL_INTERFACE:include>") | |||
set_target_properties(${PROJECT_NAME} PROPERTIES COMPILE_FLAGS "${SOFAPYTHON_COMPILER_FLAGS}") | |||
set_target_properties(${PROJECT_NAME} PROPERTIES PUBLIC_HEADER "${HEADER_FILES}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't want to be a bummer but... @guparan didn't we say we should remove all the PUBLIC_HEADER props?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, they have to go. It could also be done everywhere in a future PR.
SofaPython could not compile without having SofaExporter.
To solve that, bindings included in SofaPython are moved into SofaExporter.
Bindings should be included into their respective modules/plugins anyway.
This PR:
Reviewers will merge only if all these checks are true.