-
Notifications
You must be signed in to change notification settings - Fork 23
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
Respect YCM_USE_CMAKE_NEXT also when bootstrapping with FetchContent and fix compatibility of YCM_USE_CMAKE_NEXT=OFF with CMP0114 set to NEW #452
Conversation
This was fixed in a7e40ec .
|
As this is working fine (see https://github.com/robotology/robotology-superbuild/actions/runs/9919382871/job/27405509850), let's merge and do a release.
|
The
YCM_USE_CMAKE_NEXT
variable (that by default is consideredON
) can be used to avoid using the vendored external project by setting it toOFF
. However, the variable was not properly observed when YCM was used via FetchContent. This PR fixes this.This is useful for dealing with #50, as with this change it is possible to avoid using the vendored
ExternalProject
by just settingYCM_USE_CMAKE_NEXT
toOFF
(as we do in robotology/robotology-superbuild#1672).