Hi,

On Thu, 2008-12-18 at 19:26 -0300, Thiago Bastos wrote:
> Hi,
> 
>         Yes, but if I have a separate flag (like the memory debugging
>         one
>         mentioned) that's not linked to debug/release/whatnot, then I
>         get the
>         same issue. I don't think you can specify different flags for
>         different
>         builds with cmakesetup?
> 
> Well, if I understood the problem correctly, I think you can.
> You could use the property family "CMAKE_<LANG>_FLAGS_<CONFIG>". For
> instance, CMAKE_CXX_FLAGS_DEBUG.
> The limitation AFAIK is that any flag you set for a build type will
> affect all targets (i.e. you can't set a debug flag for only a
> specific target with this method).
> 
>  
>         Assuming that, yeah, it's a bit better than makefiles, but
>         it's not perfect.
> 
> Yeah, it's really far from perfect. But for practical purposes it's
> still the best I found so far.
> If they had used a real scripting language (e.g. Lua) and polished
> some rough edges, then it would be close to perfect :-)

hmm, not sure if I follow this one completely ;-)

Anyway, yes you can change the compiler/linker flags per
file/target from cmakelists.txt using their respective properties.
But you have to provide the logic to expose this to the configuration 
frontend.

And also yes you must use different directories, one for each variant.

As I'm going only to allow out of source builds this is not a big issue.

Running "cmake;make" is also not an issue, compared to the build times
the cmake run is neglectable. 

One problem I see right now is keeping a consistent OSGConfigured.h
file across the different builds. But event that one was not guaranteed
with scons as the last run always overrode so it was actually only valid
for that run.

One thing I have somewhere in my mind is to provide a way to export some
configured settings from one dir so other dirs can stay in sync. Kind of
a master-dir / slave-dir setup where the slave builds a different
variant but the package configurations (e.g. what ends up in
OSGConfigured.h) is enforce to be identical.

Another one is that subjectively (haven't timed it yes) the build times
have increased.




kind regards,
  gerrit



------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to