On Friday 25 January 2013, Brad King wrote: > On 01/25/2013 05:14 AM, Stephen Kelly wrote: > > Alexander Neundorf wrote: > >>> The CONFIGURE_PACKAGE_CONFIG_FILE() macro could check its > >>> INSTALL_DESTINATION argument, whether it is /lib[64]/ or /usr/lib[64]/ > >>> and use full paths in that case. > >>> > >>> I'll play around a bit with the macro. > >> > >> There is now the PackageConfigHelper_UsrMove branch on stage. > > > > Are INSTALL(EXPORT)ed files affected at all by this? Do they need to be? > > Yes, since they compute paths relative to their location in order > to be relocatable. The code that generates them may need to be > made aware of this.
I don't think so. These file should be installed into lib/, so even if lib/ is a symlink, the relative path from the targets file to the library does not cross the symlink. If it is installed into share/ (which it IMO should not), there is no symlink involved (with /usr-move). Alex -- 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
