[cmake-developers] General Config.cmake file issue on ArchLinux

Alexander Neundorf neundorf at kde.org
Mon Jan 21 16:35:00 EST 2013


On Monday 21 January 2013, Andrea Scarpino wrote:
> On Monday 21 January 2013 20:09:57 Alexander Neundorf wrote:
> > what about /include/ ?
> > This typically does not exist, but this will also make the Config.cmake
> > files fail.
> > The Config.cmake files typically reference the include/ subdir, relativ
> > to their own position. If there is no /include/, which is symlinked to
> > /usr/include/, this will fail too.
> 
> Hi, there's no /include/ in Arch.

Ok, that's actually what I expected.
This means that symlinking /lib64/ to /usr/lib/ will break most Config.cmake 
files which have been installed to /usr/lib/ (i.e. least all which do not 
hardcode the path to the include dir, but instead store it as a relative path, 
relative to the config.cmake file).

Alex






More information about the cmake-developers mailing list