On 08/10/2015 10:21 AM, [email protected] wrote:
> I often configure projects with an empty install prefix and install with
> DESTDIR set. This works for most projects and they are relocatable.
So long as projects don't contain internal references that hard-code
the prefix then relocatable packages can be built with any prefix.
Just package the binary tarball with paths relative to the staging
prefix.
> CMake Error at cmake/CMakePackageConfigHelpers.cmake:254 (file):
> file RELATIVE_PATH must be passed a full path to the file:
> Call Stack (most recent call first):
> CMakeLists.txt:157 (configure_package_config_file)
The line in question is:
file(RELATIVE_PATH PACKAGE_RELATIVE_PATH "${absInstallDir}"
"${installPrefix}" )
IIUC its purpose is to compute a relative path from the location where
the package configuration file is to be installed (absInstallDir) up
to the installation prefix (installPrefix). A special case here will
be needed to compute this for an empty install prefix.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
