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_VERIFY_INTERFACE_HEADER_SETS ---------------------------------- .. versionadded:: 3.24 This variable is used to initialize the :prop_tgt:`VERIFY_INTERFACE_HEADER_SETS` property of targets when they are created. Setting it to true enables header set verification. Projects should not normally set this variable, it is intended as a developer control to be set on the :manual:`cmake(1)` command line or other equivalent methods. The developer must have the ability to enable or disable header set verification according to the capabilities of their own machine and compiler. Verification of a dependency's header sets is not typically of interest to developers. Therefore, :command:`FetchContent_MakeAvailable` explicitly sets ``CMAKE_VERIFY_INTERFACE_HEADER_SETS`` to false for the duration of its call, but restores its original value before returning. If a project brings a dependency directly into the main build (e.g. calling :command:`add_subdirectory` on a vendored project from a git submodule), it should also do likewise. For example: .. code:: cmake # Save original setting so we can restore it later set(want_header_set_verification ${CMAKE_VERIFY_INTERFACE_HEADER_SETS}) # Include the vendored dependency with header set verification disabled set(CMAKE_VERIFY_INTERFACE_HEADER_SETS OFF) add_subdirectory(...) # Vendored sources, e.g. from git submodules # Add the project's own sources. Restore the developer's original choice # for whether to enable header set verification. set(CMAKE_VERIFY_INTERFACE_HEADER_SETS ${want_header_set_verification}) add_subdirectory(src) By default, this variable is not set, which will result in header set verification being disabled.