PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` CMAKE_TRY_COMPILE_PLATFORM_VARIABLES ------------------------------------ .. versionadded:: 3.6 List of variables that the :command:`try_compile` command source file signature must propagate into the test project in order to target the same platform as the host project. This variable should not be set by project code. It is meant to be set by CMake's platform information modules for the current toolchain, or by a toolchain file when used with :variable:`CMAKE_TOOLCHAIN_FILE`. Variables meaningful to CMake, such as :variable:`CMAKE__FLAGS`, are propagated automatically. The ``CMAKE_TRY_COMPILE_PLATFORM_VARIABLES`` variable may be set to pass custom variables meaningful to a toolchain file. For example, a toolchain file may contain: .. code-block:: cmake set(CMAKE_SYSTEM_NAME ...) set(CMAKE_TRY_COMPILE_PLATFORM_VARIABLES MY_CUSTOM_VARIABLE) # ... use MY_CUSTOM_VARIABLE ... If a user passes ``-DMY_CUSTOM_VARIABLE=SomeValue`` to CMake then this setting will be made visible to the toolchain file both for the main project and for test projects generated by the :command:`try_compile` command source file signature. .. versionchanged:: 3.24 Listed variables are propagated to the :command:`try_compile` :ref:`whole-project ` signature too. See :policy:`CMP0137`. .. versionadded:: 3.24 The :variable:`CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES` variable may be set to disable passing platform variables into the test project.