... | ... | @@ -54,14 +54,14 @@ compiler it should use, so you have to preset this too: |
|
|
Once the system and the compiler are determined by CMake, it loads the
|
|
|
corresponding files in the following order:
|
|
|
|
|
|
- Platform/${CMAKE_SYSTEM_NAME}.cmake (optional, but issues a stern
|
|
|
- `Platform/${CMAKE_SYSTEM_NAME}.cmake` (optional, but issues a stern
|
|
|
warning)
|
|
|
- Platform/${CMAKE_SYSTEM_NAME}-<compiler>.cmake
|
|
|
- `Platform/${CMAKE_SYSTEM_NAME}-<compiler>.cmake`
|
|
|
(optional)
|
|
|
- Platform/${CMAKE_SYSTEM_NAME}-<compiler>-${CMAKE_SYSTEM_PROCESSOR}.cmake
|
|
|
- `Platform/${CMAKE_SYSTEM_NAME}-<compiler>-${CMAKE_SYSTEM_PROCESSOR}.cmake`
|
|
|
(optional)
|
|
|
|
|
|
<compiler> is either the basename of the compiler executable, e.g. "gcc"
|
|
|
`<compiler>` is either the basename of the compiler executable, e.g. "gcc"
|
|
|
(this is also used if gcc has a different name) or "cl", or by a
|
|
|
compiler id, which is detected by compiling a test source file.
|
|
|
|
... | ... | @@ -289,8 +289,8 @@ There you will find all variables which CMake could not determine, from |
|
|
which CMake file they were called, the source file, the arguments for
|
|
|
the executable and the path to the executable. CMake will also copy the
|
|
|
executables in the build directory, they have the names
|
|
|
cmTryCompileExec-<name of the variable>, e.g.
|
|
|
cmTryCompileExec-SHARED_LIBRARY_PATH_TYPE. You can then try to run
|
|
|
`cmTryCompileExec-<name of the variable>`, e.g.
|
|
|
`cmTryCompileExec-SHARED_LIBRARY_PATH_TYPE`. You can then try to run
|
|
|
this executable manually on the actual target platform and check the
|
|
|
results.
|
|
|
|
... | ... | |