I use a prefix and out-of-source tree builds to install plib/osg/sg and fgfs itself.
Here is plib configuration: ---------------------------- ../../plib/configure --prefix=/opt ---------------------------- Here is how I configured sg: ---------------------------- ../../simgear/configure --with-jpeg-factory --prefix=/opt --with-osg=/opt ---------------------------- And finally fgfs: ---------------------------- ../../fgfs-base/flightgear/configure --with-osg=/opt --with-eventinput \ --with-logging --enable-osgviewer --enable-sp-fdms --prefix=/opt \ --datarootdir=/opt/fgdata ---------------------------- This assumes that OSG is installed with same prefix "/opt". You should really do out-of-source tree builds to keep your "working copy" (there where you checked out the code from repository) clean from modifications done by configure. This can be really easy archived by creating a separate "build" directory which is outside of the source code tree. Regards, Roland On Tue, 2011-04-05 at 21:58 +0800, Jin.Chengde wrote: > I put the simgear folder in the path of > /home/kent/FlightGear/simgear/include and make it > then configure the FlightGear source code > ./configure --with-simgear=/home/kent/FlightGear/simgear > then make
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
