-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Spott wrote: > Jan Ciger wrote: >> Martin Spott wrote: >>> Yes, this certainly is part of the problem .... :-/ >>> In fact, the trick is to set CFLAGS/CXXFLAGS and all these nice things >>> in the environment before running 'cmake', > >> That is not true - [...] > > No, sir, your proposal just offers yet another choice.
OK, I expressed myself wrong - the point was that you do not need to fiddle with env. variables to achieve this. > Please remember that leaving the definition of compiler flags to CMAKE > puts you at the risk of CMAKE adding flags that probably conflict with > those you have to use on your platform anyway. > > Thus setting the preferred set of compiler flags in the environment is > always the 'safe' solution for OSG, This is very arguable - nothing prevents you from customizing the build and specifying the correct/desired optimization flags there. In an enterprise environment it is actually the way to go - you have a "pre-packaged", well-defined build configuration and you are not running a risk of an unwanted change causing trouble. On Linux this isn't so much of an issue anyway because you can mix and match debug and release builds without problems. On Windows it equals to memory corruption and crashes, so I specifically wouldn't rely on environment variables to ensure the build consistency. Regards, Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGZ+UUn11XseNj94gRAiq+AJ9H6v0j0zEkbP2kOeQgYan1rfZPCgCcDCVt ljpq5nbOeo4nQjjjoIBVll8= =Hrnf -----END PGP SIGNATURE----- _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
