Re: [CMake] rpath limitations of CMake for the Cygwin platform

2007-10-30 Thread Alan W. Irwin
On 2007-10-29 20:08-0400 Bill Hoffman wrote: Alan W. Irwin wrote: I don't have access to Cygwin myself, but I have recently been getting PLplot feedback from one of our developers and also two of our more experienced users for that platform. From their detailed make and make install results

[CMake] set environment variable

2007-10-30 Thread Mark Wyszomierski
Hi, Is it possible to set an environment variable (linux) through CMake? Thanks, Mark ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] set environment variable

2007-10-30 Thread David Cole
Yes... SET(ENV{BLAH} blah value) ...but it only applies to the running process. The parent process environment remains unaffected by this type of SET. Then, to read env vars into cmake, use $ENV{BLAH} On 10/30/07, Mark Wyszomierski [EMAIL PROTECTED] wrote: Hi, Is it possible to set an

Re: [CMake] set environment variable

2007-10-30 Thread Mark Wyszomierski
Hi David, I'm new to linux, do you mean that setting the env var like that through CMake will only affect my executables during run time- in other words the env var is only set for my exes? That's fine and what I need - Mark On 10/30/07, David Cole [EMAIL PROTECTED] wrote: Yes...

Re: [CMake] set environment variable

2007-10-30 Thread David Cole
Yes, that's exactly what I mean... :-) On 10/30/07, Mark Wyszomierski [EMAIL PROTECTED] wrote: Hi David, I'm new to linux, do you mean that setting the env var like that through CMake will only affect my executables during run time- in other words the env var is only set for my exes?

Re: [CMake] set environment variable

2007-10-30 Thread Bill Hoffman
Mark Wyszomierski wrote: Hi David, I'm new to linux, do you mean that setting the env var like that through CMake will only affect my executables during run time- in other words the env var is only set for my exes? That's fine and what I need - They will only be set during cmake time. Cmake

Re: [CMake] set environment variable

2007-10-30 Thread David Cole
Oops. I misread your reply (too fast)... Bill is right. To set an env var for your executables, you'll need to write code that does it yourself. On 10/30/07, Bill Hoffman [EMAIL PROTECTED] wrote: Mark Wyszomierski wrote: Hi David, I'm new to linux, do you mean that setting the env var

[CMake] IF(string) is false. Why?

2007-10-30 Thread Brandon Van Every
IF(WHATEVER) MESSAGE(WHATEVER string is true) ELSE(WHATEVER) MESSAGE(WHATEVER string is false) ENDIF(WHATEVER) C:\devel\src\cbugs\trueorfalsecmake -P trueorfalse.cmake WHATEVER string is false I would expect the literal string WHATEVER to evaluate to true. By analogy to IF(variable) as per

Re: [CMake] IF(string) is false. Why?

2007-10-30 Thread David Cole
Because WHATEVER is not empty... I frequently use: IF(${literal_string} STREQUAL ) or: IF(NOT ${literal_string} STREQUAL ) ...to achieve this goal. It's verbose, but it works and doesn't take too much getting used to. HTH, David On 10/30/07, Brandon Van Every [EMAIL PROTECTED] wrote:

Re: [CMake] IF(string) is false. Why?

2007-10-30 Thread Brandon Van Every
On 10/30/07, David Cole [EMAIL PROTECTED] wrote: Because WHATEVER is not empty... Then it should be true. I frequently use: IF(${literal_string} STREQUAL ) or: IF(NOT ${literal_string} STREQUAL ) ...to achieve this goal. It's verbose, but it works and doesn't take too much getting used

Re: [CMake] IF(string) is false. Why?

2007-10-30 Thread Brandon Van Every
On 10/30/07, Brandon Van Every [EMAIL PROTECTED] wrote: On 10/30/07, David Cole [EMAIL PROTECTED] wrote: Because WHATEVER is not empty... Then it should be true. I say the following should set the result to valid. MACRO(NOQUOTES_ALONE literal_string result) IF(${literal_string})

Re: [CMake] IF(string) is false. Why?

2007-10-30 Thread Brandon Van Every
On 10/30/07, Brandon Van Every [EMAIL PROTECTED] wrote: On 10/30/07, Brandon Van Every [EMAIL PROTECTED] wrote: On 10/30/07, David Cole [EMAIL PROTECTED] wrote: Because WHATEVER is not empty... Then it should be true. I say the following should set the result to valid.