An issue we have with this is that this is not possible in some environments, like build servers, or if developers are not admins on their machine. Is there a way to tell CMake to look for module files into a custom directory first, before looking at the default ${CMAKE_ROOT}/Modules?
I tried, without success, to prepend the path to Embarcadero-provided one to the CMAKE_MODULE_PATH, hoping that it would cause CMake to look there first:
cmake_minimum_required(VERSION 3.14)
list(PREPEND CMAKE_MODULE_PATH “C:/Program Files (x86)/Embarcadero/Studio/21.0/cmake/Modules”)
set(CMAKE_C_COMPILER “bcc32x”)
set(CMAKE_CXX_COMPILER “bcc32x”)
project(MyProject)
CMake’s shipped modules prefer to include each other from the same root (they largely use ${CMAKE_ROOT} or ${CMAKE_CURRENT_LIST_DIR} to make absolute paths of includes of each other rather than CMAKE_MODULE_PATH-moderated searches). You’ll likely need to provide the entire include chain above the “lowest” file that you need to change and then finally hook into CMake-provided files.
See policy CMP0017. CMake does not want projects to override a builtin module that is included from another builtin module. Otherwise those modules become a public API and limits refactoring. The lack of that policy in the old days produced several cases where that caused problems, and in at least one such case we forever need to do something special in every find module to include FPHSA safely.
Embarcadero should contribute whatever changes are needed to CMake instead of telling people to modify their installations.