[CMake] Changing MD -> MT

2008-02-16 Thread Mathieu Malaterre
Hi there, While trying to compile my project in shared libs I realized it was not compiling any more with the free C++ toolkit 2003. Looking at Windows-cl.cmake the only difference I can see is that each MD flags was changed to a MT. So I decided to give it a try with the VCExpress/Nmake one,

Re: [CMake] Re: function and raise_scope commands (+ unset bug)

2008-02-16 Thread Filipe Sousa
Sebastien BARRE wrote: OK, back to PARENT_SCOPE. Well, Tcl/Tk has 'upvar' (which RAISE_SCOPE was inspired from), *and* 'global', which would pretty much declare variables inside a procedure/function to be of the "global scope" nature. I don't really like any of them. If I had to give a (crazy)

Re: [CMake] Re: function and raise_scope commands (+ unset bug)

2008-02-16 Thread Sebastien BARRE
At 2/16/2008 03:48 PM, Alexander Neundorf wrote: Would RAISE_SCOPE(var1 var2 ... varN) be better ? Why was the syntax changed from that to RAISE_SCOPE(varname value) ? (which was basically a set() and that's why converted to set(... PARENT_SCOPE) ) Sorry, I missed the fact that RAISE_SCOPE ha

Re: [CMake] parallel builds for ctest

2008-02-16 Thread Bill Hoffman
Alan W. Irwin wrote: On 2008-02-16 12:38-0500 Bill Hoffman wrote: [...]parallel ctest is on the todo list for this year. Most likely it will be ctest -j N. We can not depend on the make system to do the parallel stuff, and ctest -j would be useful for all generators. That's excellent new

Re: [CMake] Re: function and raise_scope commands (+ unset bug)

2008-02-16 Thread Alexander Neundorf
On Saturday 16 February 2008, Sebastien BARRE wrote: Hi Sebastian, ... > Hey guys, ... > Obviously foo is not set, since it is now set in SET_VAR2 scope. Bummer. > So now I have to do things like this: > > FUNCTION(SET_VAR2 varname) >SET_VAR1(varname_proxy) >SET(${varname} ${varname_proxy

Re: [CMake] Re: function and raise_scope commands (+ unset bug)

2008-02-16 Thread Sebastien BARRE
At 2/16/2008 02:13 PM, Alexander Neundorf wrote: > > I don't mean to remove the SET(PARENT_SCOPE) feature, where the main > purpose is to set a global variable from within a function. > But if SET( ... PARENT_SCOPE) is called outside a function, the effect is > that the variable is set in the par

Re: [CMake] parallel builds for ctest

2008-02-16 Thread Alan W. Irwin
On 2008-02-16 12:38-0500 Bill Hoffman wrote: [...]parallel ctest is on the todo list for this year. Most likely it will be ctest -j N. We can not depend on the make system to do the parallel stuff, and ctest -j would be useful for all generators. That's excellent news! The execution of t

Re: [CMake] Re: function and raise_scope commands

2008-02-16 Thread Alexander Neundorf
On Saturday 16 February 2008, Alexander Neundorf wrote: > On Saturday 16 February 2008, Bill Hoffman wrote: > > Alexander Neundorf wrote: > > > On Friday 18 January 2008, Alexander Neundorf wrote: > > ... > > > >> set(foo a b c PARENT_SCOPE) > > >> > > >> I'm not sure it is a good idea that this al

Re: [CMake] parallel builds for ctest

2008-02-16 Thread Bill Hoffman
David Cole wrote: Parallel tests are only going to be possible if you can guarantee that all tests are independent of all other tests, or if you specify explicit dependencies between tests somehow. (Which would introduce the same sort of complexity you complain about above for build steps..

Re: [CMake] parallel builds for ctest

2008-02-16 Thread David Cole
On 2/15/08, Alan W. Irwin <[EMAIL PROTECTED]> wrote: > > David, I may be leaping to conclusions here, but it appears from what you > have said that it is a reasonable hypothesis that the ctest commmand works > through the cmake generator backend. True When that is "make" (the default for > Unix

[CMake] Detecting changed libraries

2008-02-16 Thread Nico Galoppo
Hi, I have a project set up where I genererate optimized/debug libraries depending on the build type. In the debug build, a 'd' postfix is added with CMAKE_DEBUG_POSTFIX. However, when building the unit tests from the same project tree, the updated link library is not detected and hence the unit t

Re: [CMake] Re: function and raise_scope commands

2008-02-16 Thread Alexander Neundorf
On Saturday 16 February 2008, Bill Hoffman wrote: > Alexander Neundorf wrote: > > On Friday 18 January 2008, Alexander Neundorf wrote: ... > >> set(foo a b c PARENT_SCOPE) > >> > >> I'm not sure it is a good idea that this also propagates to the parent > >> directory. What is a use case for this ?

Re: [CMake] Re: function and raise_scope commands

2008-02-16 Thread Bill Hoffman
Alexander Neundorf wrote: On Friday 18 January 2008, Alexander Neundorf wrote: On Friday 18 January 2008, Rodolfo Schulz de Lima wrote: Miguel A. Figueroa-Villanueva wrote: Again, I think this behaviour is a quite unintuitive and should be well documented, at least. I shall add that at first

Re: [CMake] Re: function and raise_scope commands

2008-02-16 Thread Alexander Neundorf
On Friday 18 January 2008, Alexander Neundorf wrote: > On Friday 18 January 2008, Rodolfo Schulz de Lima wrote: > > Miguel A. Figueroa-Villanueva wrote: > > > Again, I think this behaviour is a quite unintuitive and should be > > > well documented, at least. > > > > I shall add that at first I expe