On Friday 17 February 2012, Eric Noulard wrote: > 2012/2/16 Brad King <brad.k...@kitware.com>: ... > > the real install location, DESTDIR, or a tarball that was extracted > > at an arbitrary location on another machine. The load-time prefix > > is computed relative to the file's location. Under that prefix the > > file refers to all the other pieces (include, etc.) which exist at > > a fixed location relative to BarConfig.cmake. > > Right I did not realize that relative position should still be valid. > In fact I'm pretty sure you can break this if you mess-up with > absolute install destination, but if ones to that there is no point in > using this so...
It works with absolute install destinations as long as they point to subdirectories of CMAKE_INSTALL_PREFIX. If they point somewhere else, they are really fixed. 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
