Re: [CMake] Macro Problem

On 07/14/2010 04:37 PM, michael.schm...@l-3com.com wrote: > Hello, > > My project has third party source in a subdirectory. The third party > source has to be compiled without special options. With autoconf, we > had "CFLAGS =". How would I do the same with cmake and restore CFLAGS > to their o

Re: [CMake] Macro Problem

In regards to this topic *in my opinion* linking directory structure/level to CMake CFLAGS is not a good design (on the part of CMake)... again *in my opinion*. I would prefer there was project level (and ability to inherit project level settings from another project using the project() where proj

Re: [CMake] Macro Problem

By default, variables (such as CMAKE_C_FLAGS and CMAKE_CXX_FLAGS) open a new nested scope with each subdirectory. So, any changes you make in a directory will only be seen in that directory and its children, not any parent or sibling directories. So, in short, you can just do what you were planni

[CMake] Macro Problem

Hello, My project has third party source in a subdirectory. The third party source has to be compiled without special options. With autoconf, we had "CFLAGS =". How would I do the same with cmake and restore CFLAGS to their original value in the parent directory? Thanks, Mike ___

Re: [CMake] CMake macro problem

Marcel Loose wrote: I have a problem with a self-written CMake macro, but I don't know exactly what the problem is. I have defined macro(SetIfElse var val def), which is supposed to assign the contents of val to var, when val is defined; otherwise it should assign the contents of def to var. Thi

[CMake] CMake macro problem

Hi, I have a problem with a self-written CMake macro, but I don't know exactly what the problem is. I have defined macro(SetIfElse var val def), which is supposed to assign the contents of val to var, when val is defined; otherwise it should assign the contents of def to var. This macro was inspi