[CMake] cpack makes good source release, but empty binary release

[Alan W. Irwin]

On 2006-12-16 06:06+0100 Thomas Arcila wrote:

> Hi,
>
> It's seems that you might be using kind of absolute path schem:

Good catch!  Indeed, PLplot needs absolute install paths
since we have a flexible autotools-like installation directory scheme with
potentially different absolute path prefixes for, e.g., libraries and
executables.

> cpack relies on modification of CMAKE_INSTALL_PREFIX to install files in
> its own directory and CMAKE_INSTALL_PREFIX is only preprended when using
> relative path with INSTALL(...) commands.
>

Thomas, thanks very much for informing me about this current CPack
limitation.

I believe I can work around this CPack limitation by checking whether all
the resultant absolute install directories we have start with
${CMAKE_INSTALL_PREFIX} (which should be the case when trying to build a
binary release), and if so, turn all the install directories into a form
relative to ${CMAKE_INSTALL_PREFIX}.  But I hope that workaround is only
needed for the short term.

Question for the CPack developers here.... Is this relative install path
limitation for CPack really necessary or just a temporary programming 
expedient that should be straightforward to fix?

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 Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________