You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When this option is used with the ONLY option, the CMAKE_PREFIX_PATH variable, that is used by the superbuild's subproject and by the YCMBootstrap to find the superbuild subprojects already installed, is ignored by find_package calls, and it is only possible to specify directories in which to search by setting the CMAKE_FIND_ROOT_PATH CMake variable. A possible solution is indeed to check in the superbuild if CMAKE_FIND_ROOT_PATH_MODE_PACKAGE is set to ONLY and propagate/set CMAKE_FIND_ROOT_PATH instead of propagating and setting CMAKE_PREFIX_PATH.
Some CMake toolchain for cross-compiling set the
CMAKE_FIND_ROOT_PATH_MODE_PACKAGE
CMake variable toONLY
. For an example of such toolchain, see Emscripten's one at : https://github.com/emscripten-core/emscripten/blob/1.38.30/cmake/Modules/Platform/Emscripten.cmake#L189 .When this option is used with the
ONLY
option, theCMAKE_PREFIX_PATH
variable, that is used by the superbuild's subproject and by the YCMBootstrap to find the superbuild subprojects already installed, is ignored byfind_package
calls, and it is only possible to specify directories in which to search by setting theCMAKE_FIND_ROOT_PATH
CMake variable. A possible solution is indeed to check in the superbuild ifCMAKE_FIND_ROOT_PATH_MODE_PACKAGE
is set toONLY
and propagate/setCMAKE_FIND_ROOT_PATH
instead of propagating and settingCMAKE_PREFIX_PATH
.cc @diegoferigo
The text was updated successfully, but these errors were encountered: