Hi Bruce, this is how I configure osg (3.0.0 ATM):
---------------- reconfigure.sh --------------
#!/bin/sh
export CFLAGS="-g -O3 -fPIC"
export CXXFLAGS="-g -O3 -fPIC"
cmake -D CMAKE_BUILD_TYPE:STRING=Release -D \
CMAKE_INSTALL_PREFIX:PATH=/opt ../../osg/
---------------- reconfigure.sh --------------
As you can see, I specify "../../osg/" which means I'm doing a so called
out-of-source-tree build. Jester told me that this has the big advantage
that the checkout (source) tree doesn't get polluted with build files so
it remains in a clean state. And you can have differently configured
source trees (e.g. one with Release, other with Debug and both with
different install prefixes).
Regards,
Roland
PS: Didn't "we" told this all some weeks ago to another guy? I would
recommend setting up a wiki page for easier build documentation and if
already done, to update it with these information.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
