On 2009-12-01 10:02+0100 Arjen Markus wrote:
> Hi Werner,
> it does exist, but changing just that variable does not make
> the others change with it. I changed that variable and ran
> the Configure step again - no change to the others.
> On 2009-12-01 10:00, Werner Smekal wrote:
>> Hi Arjen,
>> usually you set the variable CMAKE_INSTALL_PREFIX and all other
>> variables are set accordingly. Does this variable exist in the GUI?
The ccmake GUI (and presumably the Windows GUI you are using) deals with
cached variables. As far as I know, such GUI's only allow you to set cache
variables one by one with no check concerning their consistency. For
example, in the early days I tried to figure out a way to allow the ccmake
GUI user to change CMAKE_INSTALL_PREFIX and have the rest of the variables
associated with install locations changed consistently with that, but I was
unsuccessful (just like what you have experienced). It's possible we may
have missed some way to impose such consistency, and I encourage you to set
up a simple test case that attempts to set a variable options) that depends
on CMAKE_INSTALL_PREFIX to see how your cmake GUI will react to that
situation for all possible set options for the dependent variable. But for
now, I don't recommend using CMake GUI's with the PLplot build until we find
a solution (if one exists) for this inconsistency problem.
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