Files
CMake/Modules/CheckCSourceCompiles.cmake
Matthew Woehlke b88b7e7c18 Help: Fix lexing of multi-line strings
Teach our CMake lexer to recognize `[[...]]` multi-line strings, as used
in some 'check source compiles/runs' examples to pass literal C/C++ code
through a CMake function. Previously, this resulted in the lexer trying
to parse such code as CMake, which is obviously incorrect. Also, use the
new `[[` syntax in more places.

Note that, because `[[...]]` can also show up in some instances denoting
optional arguments, we only consider `[[` with no `=` as a string if the
`[[` is followed by a non-identifier character. This heuristic seems to
work for most existing usages.

Co-Authored-By: Georg Brandl <georg@python.org>
2026-02-13 13:36:59 -05:00

105 lines
3.0 KiB
CMake

# Distributed under the OSI-approved BSD 3-Clause License. See accompanying
# file LICENSE.rst or https://cmake.org/licensing for details.
#[=======================================================================[.rst:
CheckCSourceCompiles
--------------------
This module provides a command to check whether a C source can be built.
Load this module in a CMake project with:
.. code-block:: cmake
include(CheckCSourceCompiles)
Commands
^^^^^^^^
This module provides the following command:
.. command:: check_c_source_compiles
Checks once whether the given C source code can be built:
.. code-block:: cmake
check_c_source_compiles(<code> <variable> [FAIL_REGEX <regexes>...])
This command checks once that the source supplied in ``<code>`` can be
compiled (and linked into an executable). The result of the check is
stored in the internal cache variable specified by ``<variable>``.
The arguments are:
``<code>``
C source code to check. This must be an entire program, as written in
a file containing the body block. All symbols used in the source code
are expected to be declared as usual in their corresponding headers.
``<variable>``
Variable name of an internal cache variable to store the result of the
check, with boolean true for success and boolean false for failure.
``FAIL_REGEX <regexes>...``
If one or more regular expression patterns are provided, then failure is
determined by checking if anything in the compiler output matches any of
the specified regular expressions.
.. rubric:: Variables Affecting the Check
The following variables may be set before calling this command to modify
the way the check is run:
.. include:: /module/include/CMAKE_REQUIRED_FLAGS.rst
.. include:: /module/include/CMAKE_REQUIRED_DEFINITIONS.rst
.. include:: /module/include/CMAKE_REQUIRED_INCLUDES.rst
.. include:: /module/include/CMAKE_REQUIRED_LINK_OPTIONS.rst
.. include:: /module/include/CMAKE_REQUIRED_LIBRARIES.rst
.. include:: /module/include/CMAKE_REQUIRED_LINK_DIRECTORIES.rst
.. include:: /module/include/CMAKE_REQUIRED_QUIET.rst
.. include:: /module/include/CMAKE_TRY_COMPILE_TARGET_TYPE.rst
Examples
^^^^^^^^
Checking whether C source code containing SSE2 intrinsic can be compiled
and linked:
.. code-block:: cmake
include(CheckCSourceCompiles)
check_c_source_compiles([[
#include <emmintrin.h>
int main(void)
{
__m128d a = _mm_setzero_pd();
(void)a;
return 0;
}
]] PROJECT_HAVE_SSE2_INTRINSICS)
See Also
^^^^^^^^
* The :module:`CheckSourceCompiles` module for a more general command to
check whether source can be built.
* The :module:`CheckSourceRuns` module to check whether source can be built
and run.
#]=======================================================================]
include_guard(GLOBAL)
include(Internal/CheckSourceCompiles)
macro(CHECK_C_SOURCE_COMPILES SOURCE VAR)
cmake_check_source_compiles(C "${SOURCE}" ${VAR} ${ARGN})
endmacro()