Brad King wrote:
> If I'm reading that thread correctly, the conclusion was the following
> proposal:
>
> - CMAKE_INSTALL_PREFIX will be set to the install prefix in which
> files will appear on the target device. The path may not exist
> on the host anywhere. Project code may use ${CMAKE_INSTALL_PREFIX}
> to generate and compile-in paths to be used at runtime on the
> target device.
>
> - CMAKE_EXTERNAL_INSTALL_PREFIX can be set to a staging install prefix
> on the host. This value will be used to set the default for
> CMAKE_INSTALL_PREFIX inside generated cmake_install.cmake files.
> The actual install rules will still use
> $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}, but the ${CMAKE_INSTALL_PREFIX}
> in this context will be the value of CMAKE_EXTERNAL_INSTALL_PREFIX.
Sounds good to me. I haven't looked into the implementation details like
that yet, but I'll do so tomorrow.
> In other words, the project is only aware of CMAKE_INSTALL_PREFIX at
> configuration time, and CMAKE_EXTERNAL_INSTALL_PREFIX is used only at
> "make install" time to stage target-destined files on the host.
> How about the name "CMAKE_STAGING_PREFIX"?
Sounds good to me.
Thanks,
Steve.
--
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
