[CMake] faq update?

[Alan W. Irwin]

On 2007-09-13 18:08-0700 Sanchez, Juan wrote:

> The rpath is not known at compile time.  It is only known when our
internal release system is done.  Some people don't want a wrapper script
setting the LD_LIBRARY_PATH.  Others don't want to hack the binary to encode
the proper rpath after the fact.

These rpath problems may be true of your current build system, but cmake
actually takes care of these rpath issues quite nicely.  The complicated
rpath stuff that is required in the build tree (with all the libraries
potentially scattered all over the build tree) is all done automatically by
cmake without any intervention on the part of the user. The install tree
rpath has to be set up properly by the user with the appropriate
INSTALL_RPATH option to SET_TARGET_PROPERTIES, but this set up is
straightforward since generally all libraries are installed in the same
place.

I also dislike fooling around with LD_LIBRARY_PATH so I thought I should
bring this CMake positive to your attention.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________
-------------- next part --------------
_______________________________________________
CMake mailing list
CMake at cmake.org
http://www.cmake.org/mailman/listinfo/cmake