2013-10-15 19:17:36 +04:00
|
|
|
try_compile
|
|
|
|
-----------
|
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
.. only:: html
|
|
|
|
|
|
|
|
.. contents::
|
|
|
|
|
2013-10-15 19:17:36 +04:00
|
|
|
Try building some code.
|
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
Try Compiling Whole Projects
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
2013-10-15 19:17:36 +04:00
|
|
|
::
|
|
|
|
|
|
|
|
try_compile(RESULT_VAR <bindir> <srcdir>
|
2015-02-05 00:06:13 +03:00
|
|
|
<projectName> [<targetName>] [CMAKE_FLAGS <flags>...]
|
2013-10-15 19:17:36 +04:00
|
|
|
[OUTPUT_VARIABLE <var>])
|
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
Try building a project. The success or failure of the ``try_compile``,
|
|
|
|
i.e. ``TRUE`` or ``FALSE`` respectively, is returned in ``RESULT_VAR``.
|
|
|
|
|
|
|
|
In this form, ``<srcdir>`` should contain a complete CMake project with a
|
|
|
|
``CMakeLists.txt`` file and all sources. The ``<bindir>`` and ``<srcdir>``
|
|
|
|
will not be deleted after this command is run. Specify ``<targetName>`` to
|
|
|
|
build a specific target instead of the ``all`` or ``ALL_BUILD`` target. See
|
|
|
|
below for the meaning of other options.
|
|
|
|
|
|
|
|
Try Compiling Source Files
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^
|
2013-10-15 19:17:36 +04:00
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
try_compile(RESULT_VAR <bindir> <srcfile|SOURCES srcfile...>
|
2015-02-05 00:06:13 +03:00
|
|
|
[CMAKE_FLAGS <flags>...]
|
|
|
|
[COMPILE_DEFINITIONS <defs>...]
|
|
|
|
[LINK_LIBRARIES <libs>...]
|
2013-10-15 19:17:36 +04:00
|
|
|
[OUTPUT_VARIABLE <var>]
|
|
|
|
[COPY_FILE <fileName> [COPY_FILE_ERROR <var>]])
|
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
Try building an executable from one or more source files. The success or
|
|
|
|
failure of the ``try_compile``, i.e. ``TRUE`` or ``FALSE`` respectively, is
|
|
|
|
returned in ``RESULT_VAR``.
|
2013-10-15 19:17:36 +04:00
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
In this form the user need only supply one or more source files that include a
|
|
|
|
definition for ``main``. CMake will create a ``CMakeLists.txt`` file to build
|
|
|
|
the source(s) as an executable that looks something like this::
|
2013-10-15 19:17:36 +04:00
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
add_definitions(<expanded COMPILE_DEFINITIONS from caller>)
|
2013-10-15 19:17:36 +04:00
|
|
|
include_directories(${INCLUDE_DIRECTORIES})
|
|
|
|
link_directories(${LINK_DIRECTORIES})
|
2015-02-05 00:06:13 +03:00
|
|
|
add_executable(cmTryCompileExec <srcfile>...)
|
2013-10-15 19:17:36 +04:00
|
|
|
target_link_libraries(cmTryCompileExec ${LINK_LIBRARIES})
|
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
The options are:
|
|
|
|
|
|
|
|
``CMAKE_FLAGS <flags>...``
|
|
|
|
Specify flags of the form ``-DVAR:TYPE=VALUE`` to be passed to
|
|
|
|
the ``cmake`` command-line used to drive the test build.
|
|
|
|
The above example shows how values for variables
|
|
|
|
``INCLUDE_DIRECTORIES``, ``LINK_DIRECTORIES``, and ``LINK_LIBRARIES``
|
|
|
|
are used.
|
|
|
|
|
|
|
|
``COMPILE_DEFINITIONS <defs>...``
|
|
|
|
Specify ``-Ddefinition`` arguments to pass to ``add_definitions``
|
|
|
|
in the generated test project.
|
|
|
|
|
|
|
|
``COPY_FILE <fileName>``
|
|
|
|
Copy the linked executable to the given ``<fileName>``.
|
|
|
|
|
|
|
|
``COPY_FILE_ERROR <var>``
|
|
|
|
Use after ``COPY_FILE`` to capture into variable ``<var>`` any error
|
|
|
|
message encountered while trying to copy the file.
|
|
|
|
|
|
|
|
``LINK_LIBRARIES <libs>...``
|
|
|
|
Specify libraries to be linked in the generated project.
|
|
|
|
The list of libraries may refer to system libraries and to
|
|
|
|
:ref:`Imported Targets <Imported Targets>` from the calling project.
|
|
|
|
|
|
|
|
If this option is specified, any ``-DLINK_LIBRARIES=...`` value
|
|
|
|
given to the ``CMAKE_FLAGS`` option will be ignored.
|
|
|
|
|
|
|
|
``OUTPUT_VARIABLE <var>``
|
|
|
|
Store the output from the build process the given variable.
|
|
|
|
|
|
|
|
In this version all files in ``<bindir>/CMakeFiles/CMakeTmp`` will be
|
|
|
|
cleaned automatically. For debugging, ``--debug-trycompile`` can be
|
|
|
|
passed to ``cmake`` to avoid this clean. However, multiple sequential
|
|
|
|
``try_compile`` operations reuse this single output directory. If you use
|
|
|
|
``--debug-trycompile``, you can only debug one ``try_compile`` call at a time.
|
|
|
|
The recommended procedure is to protect all ``try_compile`` calls in your
|
|
|
|
project by ``if(NOT DEFINED RESULT_VAR)`` logic, configure with cmake
|
|
|
|
all the way through once, then delete the cache entry associated with
|
|
|
|
the try_compile call of interest, and then re-run cmake again with
|
|
|
|
``--debug-trycompile``.
|
|
|
|
|
|
|
|
Other Behavior Settings
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
2015-08-14 18:48:01 +03:00
|
|
|
If set, the following variables are passed in to the generated
|
|
|
|
try_compile CMakeLists.txt to initialize compile target properties with
|
|
|
|
default values:
|
|
|
|
|
2015-08-25 05:56:31 +03:00
|
|
|
* :variable:`CMAKE_ENABLE_EXPORTS`
|
2015-08-14 18:48:01 +03:00
|
|
|
* :variable:`CMAKE_LINK_SEARCH_START_STATIC`
|
|
|
|
* :variable:`CMAKE_LINK_SEARCH_END_STATIC`
|
2015-08-14 18:48:54 +03:00
|
|
|
* :variable:`CMAKE_POSITION_INDEPENDENT_CODE`
|
|
|
|
|
|
|
|
If :policy:`CMP0056` is set to ``NEW``, then
|
|
|
|
:variable:`CMAKE_EXE_LINKER_FLAGS` is passed in as well.
|
2015-08-14 18:48:01 +03:00
|
|
|
|
2015-08-25 05:56:31 +03:00
|
|
|
The current setting of :policy:`CMP0065` is set in the generated project.
|
|
|
|
|
2015-02-05 00:06:13 +03:00
|
|
|
Set the :variable:`CMAKE_TRY_COMPILE_CONFIGURATION` variable to choose
|
|
|
|
a build configuration.
|
2016-02-19 21:23:48 +03:00
|
|
|
|
|
|
|
Set the :variable:`CMAKE_TRY_COMPILE_TARGET_TYPE` variable to specify
|
|
|
|
the type of target used for the source file signature.
|