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` CMP0142 ------- .. versionadded:: 3.25 The :generator:`Xcode` generator does not append per-config suffixes to library search paths. In CMake 3.24 and below, the :generator:`Xcode` generator preceded each entry of a library search path with a copy of itself appended with ``$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)``. This was left from very early versions of CMake in which per-config directories were not well modeled. Such paths often do not exist, resulting in warnings from the toolchain. CMake 3.25 and above prefer to not add such library search paths. This policy provides compatibility for projects that may have been accidentally relying on the old behavior. The ``OLD`` behavior for this policy is to append ``$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)`` to all library search paths. The ``NEW`` behavior is to not modify library search paths. This policy was introduced in CMake version 3.25. Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly. Unlike many policies, CMake version |release| does *not* warn when this policy is not set and simply uses ``OLD`` behavior. .. include:: DEPRECATED.txt