![]() Treated as relative to the current source directory. The may reference either a sourceĭirectory or its corresponding binary directory. Schedule the call for the end of the given directory instead of theĬurrent directory. The following view depending of the content of this variable: The order depends of theįollowing rules: If CMAKE_SIZEOF_VOID_P variable is defined. TARGET Query the registry matching the architecture specified byĬMAKE_SIZEOF_VOID_P variable. HOST Query the registry matching the architecture of the host: 64 onĦ4bit Windows and 32 on 32bit Windows. For VALUE_NAMES and SUBKEYS sub-options, queryīoth views ( 32 and 64) and merge the results (sorted andĭuplicates removed). View 32, and if the request failed, query the registry using viewĦ4. 32_64 For VALUE sub-option or default value, query the registry using For VALUE_NAMES and SUBKEYS sub-options, queryīoth views ( 64 and 32) and merge the results (sorted andĭuplicates removed). View 64, and if the request failed, query the registry using viewģ2. 64_32 For VALUE sub-option or default value, query the registry using On 32bit Windows, returns always an empty Query Windows registryĦ4 Query the 64bit registry. Unset(CMAKE_GET_OS_RELEASE_FALLBACK_CONTENT) FOOTNOTES One MiB (mebibyte) is equal to 1024x1024 bytes. If(NOT EXISTS "$)ĪPPEND CMAKE_GET_OS_RELEASE_FALLBACK_RESULTĬMAKE_GET_OS_RELEASE_FALLBACK_RESULT_NAMEĬMAKE_GET_OS_RELEASE_FALLBACK_RESULT_PRETTY_NAMEĬMAKE_GET_OS_RELEASE_FALLBACK_RESULT_VERSIONĬMAKE_GET_OS_RELEASE_FALLBACK_RESULT_VERSION_ID Os-release) if it exists in the /etc/os-release file into a list of read variables DISTRIB_ New in version 3.22. ![]() Read /etc/os-release file and define the given See CMAKE_HOST_SYSTEM_PROCESSOR DISTRIB_INFO New in version 3.22. The OS build ID OS_PLATFORM New in version 3.10. on Windows Professional OS_VERSION New in version 3.10. See CMAKE_HOST_SYSTEM_NAME OS_RELEASE New in version 3.10. Human readable full processor description OS_NAME New in version 3.10. Human readable processor name PROCESSOR_DESCRIPTION New in version 3.10. Processor serial number PROCESSOR_NAME New in version 3.10. One if processor has serial number PROCESSOR_SERIAL_NUMBER New in version 3.10. One if IA64 processor emulating x86 HAS_SERIAL_NUMBER New in version 3.10. One if processor supports 3DNow+ instructions HAS_IA64 New in version 3.10. One if processor supports 3DNow instructions HAS_AMD_3DNOW_PLUS New in version 3.10. One if processor supports SSE MMX instructions HAS_AMD_3DNOW New in version 3.10. One if processor supports SSE FP instructions HAS_SSE_MMX New in version 3.10. One if processor supports SSE2 instructions HAS_SSE_FP New in version 3.10. One if processor supports SSE instructions HAS_SSE2 New in version 3.10. MMX instructions HAS_SSE New in version 3.10. One if processor supports MMX instructions HAS_MMX_PLUS New in version 3.10. One if processor has floating point unit HAS_MMX New in version 3.10. One if processor is 64Bit HAS_FPU New in version 3.10. If parsing the cmakelists is too complex for this (especially since often ExternalProject_Add is called by included functions), i'd suggest simply allowing to specify more than one compile_commands.json file.NUMBER_OF_LOGICAL_CORES Number of logical cores NUMBER_OF_PHYSICAL_CORES Number of physical cores HOSTNAME Hostname FQDN Fully qualified domain name TOTAL_VIRTUAL_MEMORY Total virtual memory in MiB AVAILABLE_VIRTUAL_MEMORY Available virtual memory in MiB TOTAL_PHYSICAL_MEMORY Total physical memory in MiB AVAILABLE_PHYSICAL_MEMORY Available physical memory in MiB IS_64BIT New in version 3.10. when built, additional compile_commands.json files will be generated in the external project's BINARY_DIR (often, but not always, a subfolder of the main project's BINARY_DIR, can be specified in ExternalProject_Add).when configured, build/compile_commands.json will contain the commands specified in /CMakeLists.txt itself./CMakeLists.txt ExternalProject_Adds /subproject/CMakeLists.txt (or anything else really, even remote git repos.This also isn't a multi-workspace/root issue. Could this be reopened? having the same exact issue, and while OP didn't explain exactly what they meant when asked, i feel this is still valid for this ticket: the use case is specified, if you read "external projects" as "calls to ExternalProject_Add".
0 Comments
Leave a Reply. |