-
Notifications
You must be signed in to change notification settings - Fork 68
Use a temporary build directory for Python module output #303
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
Use a temporary build directory for Python module output #303
Conversation
|
If the current setup fails on the buildfarm, why haven't that failed earlier? Or is it that simple, nobody released a python node using this library? |
From what I see, we are the first 😎 |
christophfroehlich
left a comment
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.
The result looks good, just not sure if there is a more cmake-native way in fixing this. So, waiting for another review.
btw: I remembered that we had an issue about python install location, but it was in setup.py configs #206.
|
@christophfroehlich Any chance this gets merged and released soon? I'm getting a lot of spam from ROS buildfarm about failing jobs... |
sea-bass
left a comment
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.
This looks good at a glance!
My only question (from limited experience working in this package): how does this change affect symlink-install and/or merge-install workflows, if at all? Maybe worth a quick test
In symlink-install, the generator python module in install directory will be symlinked to the one created in the temp build directory. The merge-install is not affected at all. |
|
I've tested the three options now with generate_parameter_module_example, I don't see any downsides. |
72887f5
into
PickNikRobotics:main
|
@bjsowa Now our example_module fails on the buildfarm Any idea how to fix this? |
It doesn't seem related as |
* Use a temporary build directory for Python module output (PickNikRobotics#303) * Added missing gmock/gtest dependency (PickNikRobotics#304) --------- Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com> Co-authored-by: Christoph Froehlich <christoph.froehlich@ait.ac.at> * make scripts accessible to find_program cmake function. --------- Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com> Co-authored-by: Błażej Sowa <bsowa123@gmail.com> Co-authored-by: Alejandro Hernández Cordero <ahcorde@gmail.com> Co-authored-by: Christoph Froehlich <christoph.froehlich@ait.ac.at> Co-authored-by: Alexandre Arnoux <alexandre.arnoux@deepx.co.jp> Co-authored-by: alexandre-arnoux-dx <148032753+AArnouxDeepX@users.noreply.github.com>
|
Oh my bad, I have tested the options with the wrong package above 🙈 Just tested now also successfully with |
The
generate_parameter_modulemacro outputs the Python module toCMAKE_INSTALL_DIRduring the build phase. This results in build failures on the ROS buildfarm due to permission errors (example here)This PR modifies the macro to output the module to a temporary directory in
CMAKE_CURRENT_BINARY_DIRand install it toCMAKE_INSTALL_DIRduring the install phase.