Re: [CMake] Re: CMAKE_INSTALL_PREFIX and DESTDIR

2008-02-22 Thread Hendrik Sattler
Am Freitag 22 Februar 2008 schrieb Fernando Cacciola: > I expected DESTDIR to be used to *completely define* the folder where the > libray is intalled, overriding the system-dependent default location > decided at configuration time, but I just realise that this not the way > DESTDIR works (with or

[CMake] Re: CMAKE_INSTALL_PREFIX and DESTDIR

2008-02-22 Thread Fernando Cacciola
Hi Mike, I don't understand. If the "user" wants to have a destination other than the default provided by CMake, why don't they just run ccmake/ cmakesetup and set the CMAKE_INSTALL_PREFIX to what they want? CMake generated project files/makefiles can only be used on the system they were genera

Re: [CMake] absolute rpath

2008-02-22 Thread Jörg Becker
On Wednesday, 20. February 2008 19:01:55 Alexander Neundorf wrote: > Use: > set_target_properties(hello PROPERTIES  INSTALL_RPATH . ) > This doesn't work, too. The problem may be, that I don't understand the path expansion in cmake (or it is buggy). I tried the following things (with set_target_p

Re: [CMake] CMAKE_INSTALL_PREFIX and DESTDIR

2008-02-22 Thread Mike Jackson
I don't understand. If the "user" wants to have a destination other than the default provided by CMake, why don't they just run ccmake/ cmakesetup and set the CMAKE_INSTALL_PREFIX to what they want? CMake generated project files/makefiles can only be used on the system they were generated on

[CMake] Re: CMAKE_INSTALL_PREFIX and DESTDIR

2008-02-22 Thread Fernando Cacciola
Fernando Cacciola wrote: string( LENGTH "$ENV{DESTDIR}" DESTDIRLEN ) if ( ${DESTDIRLEN} GREATER 0 ) message( STATUS "DESTDIR specified ($ENV{DESTDIR}). Overriding CMAKE_INSTALL_PREFIX (${CMAKE_INSTALL_PREFIX})" ) set( CMAKE_INSTALL_PREFIX "" CACHE PATH "Use DESTDIR *instead* of CMAKE_INSTALL_P

[CMake] Re: Re: IF( ${VAR} ) behaviour

2008-02-22 Thread Fernando Cacciola
Sylvain Benner wrote: Now, why didn't if ( $ENV{SOME_ENV_VAR} ) work? Because $ENV{SOME_ENV_VAR} has the same behavior as ${SOME_ENV_VAR}, it evaluates a variable. The only difference is that ${} is a CMake variable and $ENV{} is an operating system environment variable. OK, now I think a

Re: [CMake] Re: IF( ${VAR} ) behaviour

2008-02-22 Thread Sylvain Benner
Now, why didn't if ( $ENV{SOME_ENV_VAR} ) work? Because $ENV{SOME_ENV_VAR} has the same behavior as ${SOME_ENV_VAR}, it evaluates a variable. The only difference is that ${} is a CMake variable and $ENV{} is an operating system environment variable. I assume that IF statement only sca

[CMake] Re: IF( ${VAR} ) behaviour

2008-02-22 Thread Fernando Cacciola
Sylvain Benner wrote: Hi, You should use IF(VAR) instead. !! Of course !! I got confused because what I really tried at first, but didn't work, was this: if ( $ENV{SOME_ENV_VAR} ) so I figured I needed to "load" the enviroment variable into a cmake variable first, for which I added: s

[CMake] CMAKE_INSTALL_PREFIX and DESTDIR

2008-02-22 Thread Fernando Cacciola
Hi people, In 2.4.5 make install DESTDIR=/path/to/dir puts files in /path/to/dir/usr/local that's because the actual destination is $ENV{DESTDIR}/${CMAKE_INSTALL_PREFIX} Is this the expected behaviour? or is it a bug in 2.4.5? If this is expected, what is the best way to allow users to hav

Re: [CMake] IF( ${VAR} ) behaviour

2008-02-22 Thread Sylvain Benner
Fernando Cacciola a écrit : Hi people, Consider the following (tested in 2.4.7): set ( VAR "whatever" ) message( STATUS "VAR=${VAR}" ) if ( ${VAR} ) message( STATUS "VAR evaluates to true" ) else ( ${VAR} ) message( STATUS "VAR evaluates to false" ) endif( ${VAR} ) it prints "VAR eval

AW: [CMake] IF( ${VAR} ) behaviour

2008-02-22 Thread Gerhard Grimm
Hi Fernando, the code lines set ( VAR "whatever" ) if ( ${VAR} ) result in the "IF" command testing the variable "whatever" - which has not been set and thus evaluates to false. You probably wanted to use if ( VAR ) to evaluate the status of VAR. Regards, Gerhard -Ursprüngliche Nachrich

[CMake] IF( ${VAR} ) behaviour

2008-02-22 Thread Fernando Cacciola
Hi people, Consider the following (tested in 2.4.7): set ( VAR "whatever" ) message( STATUS "VAR=${VAR}" ) if ( ${VAR} ) message( STATUS "VAR evaluates to true" ) else ( ${VAR} ) message( STATUS "VAR evaluates to false" ) endif( ${VAR} ) it prints "VAR evaluates to false". Is that expec

Re: [CMake] How to prevent relinking targets with shared libraries

2008-02-22 Thread BlinkEye
On Fri, February 22, 2008 10:07, Bill Hoffman wrote: > BlinkEye wrote: >> On Thu, February 21, 2008 22:23, Alan W. Irwin wrote: >>> On 2008-02-21 21:57+0100 blinkeye wrote: [...]At the moment I'm just creating plain .so libs, without any version number (so far I didn't happen to come acr

Re: [CMake] Re: Changing MD -> MT (+patch for free toolkit)

2008-02-22 Thread Mathieu Malaterre
On Tue, Feb 19, 2008 at 5:42 PM, Gonzalo Garramuño <[EMAIL PROTECTED]> wrote: > Mathieu Malaterre wrote: > > On Feb 19, 2008 5:43 AM, Gonzalo Garramuño <[EMAIL PROTECTED]> wrote: > >> Mathieu Malaterre wrote: > >>> Ok this was yet-another-weird-dll thingy, one cannot do: > >>> > >>> class GDCM

Re: [CMake] How to prevent relinking targets with shared libraries

2008-02-22 Thread Bill Hoffman
BlinkEye wrote: On Thu, February 21, 2008 22:23, Alan W. Irwin wrote: On 2008-02-21 21:57+0100 blinkeye wrote: [...]At the moment I'm just creating plain .so libs, without any version number (so far I didn't happen to come across a shared library tutorial with cmake), maybe this is the problem