-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add BUILD_WITHOUT_DEPENDENCIES CMake option and nodeps CMake preset #697
Conversation
This functionality is meant to be used with the option added to robotology-superbuild in robotology/robotology-superbuild#1775 . |
Just to understand, how is the install prefix set? |
That is part of the CMake preset, i.e. in https://github.com/robotology/robots-configuration/pull/697/files#diff-1712b235e02bd4a3ad866fe26447a6dc5c1b449faeea513f449d244d46d03cf5R21 . Note that that is only a default, so you can still change it by calling |
I thought it was set somewhere in the |
Co-authored-by: Stefano Dafarra <[email protected]>
Yes, it may break the POLA if you are not used to |
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.
Thanks @traversaro for your contribution!
This PR adds the
BUILD_WITHOUT_DEPENDENCIES
CMake option (that by default isOFF
) and thenodeps
CMake preset to easily enableBUILD_WITHOUT_DEPENDENCIES
andINSTALL_ALL_ROBOTS
CMake option.The
BUILD_WITHOUT_DEPENDENCIES
CMake options drops any dependency on YCM, YARP and ICUBcontrib with the following limitations:yarp_install
does instead)uninstall
target (but unix users can easily uninstall anyhow withxargs rm < install_manifest.txt
)CMAKE_INSTALL_PREFIX
to the ICUBcontrib install prefixFurthermore, a
nodeps
CMake preset is added, to permit to easily build and install the CMake project with the optionsBUILD_WITHOUT_DEPENDENCIES
andINSTALL_ALL_ROBOTS
option enabled.In particular, this functionality can be used to easily create an install of robots-configuration with the commands and make it available to YARP with:
As this workflow is quite advanced and is meant just to be used in specific IIT-internal setups, I would avoid to document it in the README, and just document it where it is going to be used.