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` CMP0087 ------- .. versionadded:: 3.14 :command:`install(CODE)` and :command:`install(SCRIPT)` support generator expressions. In CMake 3.13 and earlier, :command:`install(CODE)` and :command:`install(SCRIPT)` did not evaluate generator expressions. CMake 3.14 and later will evaluate generator expressions for :command:`install(CODE)` and :command:`install(SCRIPT)`. The ``OLD`` behavior of this policy is for :command:`install(CODE)` and :command:`install(SCRIPT)` to not evaluate generator expressions. The ``NEW`` behavior is to evaluate generator expressions for :command:`install(CODE)` and :command:`install(SCRIPT)`. Note that it is the value of this policy setting at the end of the directory scope that is important, not its setting at the time of the call to :command:`install(CODE)` or :command:`install(SCRIPT)`. This has implications for calling these commands from places that have their own policy scope but not their own directory scope (e.g. from files brought in via :command:`include()` rather than :command:`add_subdirectory()`). This policy was introduced in CMake version 3.14. CMake version |release| warns when the policy is not set and uses ``OLD`` behavior. Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. .. include:: DEPRECATED.txt