Now..... I have built FlightGear on Mac OS X. After a LOT of trial and error building SimGear and FlightGear without the X11 SDK.
It seems all that needed to be done was change GL/gl.h and GL/glu.h in all the source files which contained those includes to OpenGL/*. What needs to be done is to make a patch that include GL/* on other systems but OpenGL/* on Mac OS X. I believe this would make compiling SimGear and FlightGear on Mac OS X pain less. I had to make, make clean, make again in order to find all the problems. A patch is coming! So, next I'll be making a Mac OS X package of FlightGear, and make a double-clickable application for it. On Sat, 13 Nov 2004 12:35:26 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: > If I recall correctly. OpenAL was required for PLIB. And it is not > included in Panther although it will be in Tiger. Maybe that should be > added? > > > > > On Fri, 12 Nov 2004 09:12:43 -0800, Adam Dershowitz > <[EMAIL PROTECTED]> wrote: > > OK, > > I took a whack at drafting up a new set of Mac build instructions for the > > users guide. I would appreciate it if someone else could try to run through > > this step by step just to confirm that I did not miss anything (another set > > of eyes and a different computer is pretty useful for checking.). > > > > Arthur, since you are trying a bunch, perhaps you can start completely from > > scratch and just follow through these instructions step by step. It might > > help you and it might help get them checked. > > > > Anyway, I hope this is helpful. If anyone has any other edits or > > suggestions I would be happy to hear them or just pass them directly to > > Martin. > > > > --Adam > > > > And here are is the new procedure: > > > > How to build FlightGear v0.9.6 on Mac OS X. > > > > These steps worked fine for me, but I don't know if other OS versions etc. > > might also work: > > Mac OS 10.3.6 > > XCode 1.5 > > By default this included gcc 3.3, autotmake 1.6.3, autoconf 2.53, so > > nothing else is required. > > > > * Setup the build environment: > > Create the directory to build into, and one for the source. For example: > > mkdir FlightGear > > mkdir FlightGear/src > > then I like to just create an environment variable to this: > > export BUILDDIR=/where/ever/you/created/FlightGear > > > > * Download PLIB > > I first tried to use plib 1.8.3 but that will not compile properly on a Mac > > without a few changes. But, as of this writing, the CVS version will. > > You can either use CVS, or grab the snapshot from here: > > http://plib.sourceforge.net/dist/current.tgz > > > > If you open the above link it should automatically unpack to create a folder > > called plib. > > Drag (or copy) that folder into /where/ever/you/created/FlightGear/src > > > > * Build PLIB > > > > > cd $BUILDDIR/src/plib > > > ./autogen.sh > > > ./configure --prefix=$BUILDDIR > > > make install > > > > * Get SimGear sources > > > > > cd $BUILDDIR/src > > > > > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.3 login > > # Enter "guest" for password > > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.3 -z3 co > > SimGear > > > > * Build SimGear > > > > > cd $BUILDDIR/src/SimGear > > > ./autogen.sh > > > ./configure --prefix=$BUILDDIR > > > make install > > > > * Get FlightGear sources > > Here you can either download the released source from the web site, or use > > the CVS snapshot. > > > cd $BUILDDIR/src > > For CVS do this: > > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login > > > CVS passwd: guest > > > cvs -z3 -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co > > source > > > > If you want to just grab the release, then get it from the web site, and put > > the code into src. > > > > * Build FlightGear > > > > > cd $BUILDDIR/src/FlightGear > > > ./autogen.sh > > > ./configure --prefix=$BUILDDIR --without-x > > > make > > > > * Get the base data files (if you don't have them already) > > again, you can just do a download from the web site, or you can use CVS. > > For CVS do this: > > > > > cd $BUILDDIR (or where ever you want to put the data) > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login > > CVS passwd: guest > > cvs -z3 -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co > > data > > > > * You are now ready to run FlightGear. There are a few different ways to do > > it. > > If you just do: > > > cd $BUILDDIR > > > src/FlightGear/src/Main/fgfs --fg-root=/path/to/data > > It should run. > > I believe that it will also try to search in $BUILDDIR/fgfsbase for data. > > Finally it will search for a file in your home directory .fgfsrc when it > > tries to start. You can put any startup flags that you want into that file. > > For example, if you put --fg-root=/path/to/data into that file, then you > > double click on src/FlightGear/src/Main/fgfs (or run it from the command > > line) then it should startup and run. > > > > Once it is built, you can move fgfs anywhere that you want, such as into the > > Applications folder. > > > > > From: Martin Spott <[EMAIL PROTECTED]> > > > Organization: home > > > Reply-To: FlightGear developers discussions > > > <[EMAIL PROTECTED]> > > > Newsgroups: list.flightgear-devel > > > Date: Thu, 11 Nov 2004 22:00:48 +0000 (UTC) > > > To: <[EMAIL PROTECTED]> > > > > > > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > > > [EMAIL PROTECTED] wrote: > > > > > >> Do you think you might be able to modify the mac os x docs for 0.9.6 > > >> especially with regard to updating make tools for a successful source > > >> build? > > > > > > I'd welcome any sort of submission for documentation updates. This > > > would be a great idea to get me back to working on the manual .... > > > sheeezzzz .... > > > I'd be happy to accept simple text and I will take care of converting > > > this into LaTeX to match the existing layout, > > > > > > Martin. > > > -- > > > Unix _IS_ user friendly - it's just selective about who its friends are ! > > > -------------------------------------------------------------------------- > > > > > > _______________________________________________ > > > Flightgear-devel mailing list > > > [EMAIL PROTECTED] > > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > > 2f585eeea02e2c79d7b1d8c4963bae2d > > > > _______________________________________________ > > Flightgear-devel mailing list > > [EMAIL PROTECTED] > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > 2f585eeea02e2c79d7b1d8c4963bae2d > > > > > -- > <Arthur/> > -- <Arthur/> _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d