Brad King wrote: >>> If that problem manifests in practice we can add a special hook to >>> enable the workaround. >> >> If I understand you, this doesn't sound like an attractive solution to >> me. > > If we go with CMAKE_TARGET_INSTALL_PREFIX as I describe above > then we can simply use that to activate the workaround logic > instead of CMAKE_INSTALL_PREFIX. On host-only builds the two > values will be the same and it will just work as it does now.
Ok. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
