[cmake-developers] Making Config.cmake files easier to write
Alexander Neundorf
neundorf at kde.org
Fri Feb 17 03:10:36 EST 2012
On Friday 17 February 2012, Eric Noulard wrote:
> 2012/2/16 Brad King <brad.king at 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
More information about the cmake-developers
mailing list