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_FIND_NO_INSTALL_PREFIX ---------------------------- Exclude the values of the :variable:`CMAKE_INSTALL_PREFIX` and :variable:`CMAKE_STAGING_PREFIX` variables from :variable:`CMAKE_SYSTEM_PREFIX_PATH`. CMake adds these project-destination prefixes to :variable:`CMAKE_SYSTEM_PREFIX_PATH` by default in order to support building a series of dependent packages and installing them into a common prefix. Set ``CMAKE_FIND_NO_INSTALL_PREFIX`` to ``TRUE`` to suppress this behavior. The :variable:`CMAKE_SYSTEM_PREFIX_PATH` is initialized on the first call to a :command:`project` or :command:`enable_language` command. Therefore one must set ``CMAKE_FIND_NO_INSTALL_PREFIX`` before this in order to take effect. A user may set the variable as a cache entry on the command line to achieve this. Note that the prefix(es) may still be searched for other reasons, such as being the same prefix as the CMake installation, or for being a built-in system prefix.