Re: [Flightgear-devel] Re: FlightGear on Mac OS X
OK, I have finally gotten it to build from scratch correctly. At the end of this is the build instructions. But they will only work if a set of patches are applied. I am not sure who they should go to, so that they will get put into CVS. So I have just attached them here. If none of you can apply these patches, can someone let me know who they should go to? Note that one of the problem files is a new test file that was added and shows up in CVS, so I have just commented out the problem lines in Network/ATC-Inputs.cxx so that it will compile, but the current version of that file will not work. -- Adam 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 and install OpenAL. You can build it yourself, or you can just download an installer from: http://www.openal.org/downloads.html Then click on Creative OpenAL page, and click on the MacOS X installer. The link is: http://developer.creative.com/articles/article.asp?cat=1&sbcat=31&top=38&aid =97&file=OpenAL_Installer_OSX.dmg but I gave the above path, steps just in case this link breaks. Double click on the disk image and double click on the installer. * 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 For CVS: > cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/plib login password "guest" > cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/plib -z3 co plib * 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/source > ./autogen.sh Automake should do the next two steps, but for some reason does not for FlightGear (but it does for SimGear, which is odd) > ln -s /usr/share/automake-1.6/config.guess config.guess > ln -s /usr/share/automake-1.6/config.sub config.sub > ./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, and you can run it from the command line, or by double clicking on it (if you have created ~/.fgfsrc with the flags that you want.) FlightGear_diffs.txt Description: Binary data SimGear_diffs.txt Description: Binary data ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Yes, that is correct. But I think that it is more consistent to do it by putting it into simgear/compiler.h, so I am attempting to do that right now. Give me a little while before you do any work on it. I almost have SimGear done, and FG should be easier. -- Adam > From: Arthur Wiebe <[EMAIL PROTECTED]> > Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> > Date: Tue, 16 Nov 2004 18:31:25 -0500 > To: FlightGear developers discussions <[EMAIL PROTECTED]> > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > Hey, Is this correct? > > #ifdef __APPLE__ > #include > #else > #include > #endif > > > On Tue, 16 Nov 2004 18:11:40 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: >> Dito. >> >> I will attempt to make a patch for both flightgear and simgear that >> can be checked into CVS. >> It sounds like a simple enough task. >> >> If you don't hear anything from me soon It's not working. (Or I ran out of >> time) >> >> On Tue, 16 Nov 2004 08:57:11 -0800, Adam Dershowitz >> >> >> <[EMAIL PROTECTED]> wrote: >>> Not yet. >>> Seems that there are some patches necessary. They are just ifdef stuff, but >>> it will require a few changes to CVS, to make it easy to build. I think >>> that it is a better idea to get those changes into CVS, then to put all the >>> patches into the build instructions. >>> I will try to get to it, but, like a lot of folks here, I am pretty busy. >>> If anyone else gets to it, then we can finish up the docs. >>> >>> -- Adam >>> >>> >>>> From: Martin Spott <[EMAIL PROTECTED]> >>>> Organization: home >>>> Reply-To: FlightGear developers discussions >>>> <[EMAIL PROTECTED]> >>>> Newsgroups: list.flightgear-devel >>>> Date: Mon, 15 Nov 2004 11:23:21 + (UTC) >>>> To: <[EMAIL PROTECTED]> >>>> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X >>> >>> >>>> >>>> Adam Dershowitz wrote: >>>> >>>>> 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.). >>>> >>>> Well, do Mac users consider this as ready for inclusion into the manual ? >>>> To be honest, I'd be happy if Adam would post a revides version which >>>> includes the feedback what we have seen on this list and probably >>>> off-list. >>>> >>>> Thanks, >>>> 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 >>> >> >> >> -- >> >> > > > -- > > > ___ > 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Dito. I will attempt to make a patch for both flightgear and simgear that can be checked into CVS. It sounds like a simple enough task. If you don't hear anything from me soon It's not working. (Or I ran out of time) On Tue, 16 Nov 2004 08:57:11 -0800, Adam Dershowitz <[EMAIL PROTECTED]> wrote: > Not yet. > Seems that there are some patches necessary. They are just ifdef stuff, but > it will require a few changes to CVS, to make it easy to build. I think > that it is a better idea to get those changes into CVS, then to put all the > patches into the build instructions. > I will try to get to it, but, like a lot of folks here, I am pretty busy. > If anyone else gets to it, then we can finish up the docs. > > -- Adam > > > > From: Martin Spott <[EMAIL PROTECTED]> > > Organization: home > > Reply-To: FlightGear developers discussions > > <[EMAIL PROTECTED]> > > Newsgroups: list.flightgear-devel > > Date: Mon, 15 Nov 2004 11:23:21 +0000 (UTC) > > To: <[EMAIL PROTECTED]> > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > > > Adam Dershowitz wrote: > > > >> 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.). > > > > Well, do Mac users consider this as ready for inclusion into the manual ? > > To be honest, I'd be happy if Adam would post a revides version which > > includes the feedback what we have seen on this list and probably > > off-list. > > > > Thanks, > > 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 > -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Hey, Is this correct? #ifdef __APPLE__ #include #else #include #endif On Tue, 16 Nov 2004 18:11:40 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: > Dito. > > I will attempt to make a patch for both flightgear and simgear that > can be checked into CVS. > It sounds like a simple enough task. > > If you don't hear anything from me soon It's not working. (Or I ran out of > time) > > On Tue, 16 Nov 2004 08:57:11 -0800, Adam Dershowitz > > > <[EMAIL PROTECTED]> wrote: > > Not yet. > > Seems that there are some patches necessary. They are just ifdef stuff, but > > it will require a few changes to CVS, to make it easy to build. I think > > that it is a better idea to get those changes into CVS, then to put all the > > patches into the build instructions. > > I will try to get to it, but, like a lot of folks here, I am pretty busy. > > If anyone else gets to it, then we can finish up the docs. > > > > -- Adam > > > > > > > From: Martin Spott <[EMAIL PROTECTED]> > > > Organization: home > > > Reply-To: FlightGear developers discussions > > > <[EMAIL PROTECTED]> > > > Newsgroups: list.flightgear-devel > > > Date: Mon, 15 Nov 2004 11:23:21 + (UTC) > > > To: <[EMAIL PROTECTED]> > > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > > > > > > > Adam Dershowitz wrote: > > > > > >> 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.). > > > > > > Well, do Mac users consider this as ready for inclusion into the manual ? > > > To be honest, I'd be happy if Adam would post a revides version which > > > includes the feedback what we have seen on this list and probably > > > off-list. > > > > > > Thanks, > > > 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 > > > > > -- > > -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Not yet. Seems that there are some patches necessary. They are just ifdef stuff, but it will require a few changes to CVS, to make it easy to build. I think that it is a better idea to get those changes into CVS, then to put all the patches into the build instructions. I will try to get to it, but, like a lot of folks here, I am pretty busy. If anyone else gets to it, then we can finish up the docs. -- Adam > From: Martin Spott <[EMAIL PROTECTED]> > Organization: home > Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> > Newsgroups: list.flightgear-devel > Date: Mon, 15 Nov 2004 11:23:21 + (UTC) > To: <[EMAIL PROTECTED]> > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > Adam Dershowitz wrote: > >> 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.). > > Well, do Mac users consider this as ready for inclusion into the manual ? > To be honest, I'd be happy if Adam would post a revides version which > includes the feedback what we have seen on this list and probably > off-list. > > Thanks, > 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
On 14 Nov 2004, at 13:42, Arthur Wiebe wrote:
What needs to be done is something like this
if (defined("macintosh") {
#include
}
else {
#include
}
Can you tell that I don't program in C? :)
Two things - please use __APPLE__ to detect OS-X, 'macintosh' is more
for Classic era stuff (though still works, of course)
Secondly, Flightgear in most places has #defines for gl.h and glu.h,
which are setup by configure. The files you have encountered are the
ones that have been added since I sent Curt the changes (probably two
years ago) for the FG_GL stuff, I think.
My current inclination (which I've done in other projects) is to make a
'fg_gl.h' which simply includes the #ifdef test you have above, and use
that everywhere instead of the system GL headers. This needs to be done
for glu, glut and gtlext.h as well, of course.
The reason I haven't done that yet is, SDL already has a header that
does this (SDL/SDL_gl.h), any scene graph FG switches to will also do
this, and PLIB probably ought to be doing it, I'm just too busy to
fight to get patches into plib. Doing it locally in FG will work, of
course, but is slightly redundant.
BTW, I have local changes to built with XCode, run as a bundle, with
PLIB and SimGear as private frameworks, I'm just having some SDL
startup issues I haven't had time to look at.
H&H
James
--
Morbo finds all humans pathetic
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Adam Dershowitz wrote: > 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.). Well, do Mac users consider this as ready for inclusion into the manual ? To be honest, I'd be happy if Adam would post a revides version which includes the feedback what we have seen on this list and probably off-list. Thanks, 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Patches for FlightGear and SImgear (CVS) available
http://awiebe.blogdns.net/download/patches/flightgear.patch
http://awiebe.blogdns.net/download/patches/simgear.patch
These patches were created using "cvs diff -u"
The patches should be applied before you build and will only work on
Mac OS X because if you apply this patch on Linux or Windows it won't
be able to find the headers again :)
What needs to be done is something like this
if (defined("macintosh") {
#include
}
else {
#include
}
Can you tell that I don't program in C? :)
On Sun, 14 Nov 2004 04:01:56 -0500, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> >
> Arthur,
>
> > I have built FlightGear on Mac OS X. After a LOT of trial and error
> > building SimGear and FlightGear without the X11 SDK.
> >
>
> Great!
>
> > 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/*.
> >
>
> I was really concerned why I could build without these Gl errors and
> you couldn't on mac os x so I did some research
>
> I have open GL headers in
>
> /System/Library/Frameworks/OpenGL.framework/Versions/A/Headers
>
> and
>
> /System/Library/Frameworks/AGL.framework/Versions/A/Headers
>
> If I do a 'grep -r "GL" * from ./src/flightgear/src, I get (among other
> things)
>
> FDM/.deps/MagicCarpet.Po: /FlightGear/fgdev9.6/include/GL/gl.h \
> FDM/.deps/MagicCarpet.Po:
> /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \
> FDM/.deps/MagicCarpet.Po:/FlightGear/fgdev9.6/include/GL/gl.h:
> FDM/.deps/MagicCarpet.Po:/System/Library/Frameworks/OpenGL.framework/
> Headers/gl.h:
> FDM/.deps/UFO.Po: /FlightGear/fgdev9.6/include/GL/gl.h \
> FDM/.deps/UFO.Po:
> /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \
> FDM/.deps/UFO.Po:/FlightGear/fgdev9.6/include/GL/gl.h:
> FDM/.deps/UFO.Po:/System/Library/Frameworks/OpenGL.framework/Headers/
> gl.h:
> FDM/Balloon/.deps/BalloonSim.Po: /FlightGear/fgdev9.6/include/GL/gl.h \
> FDM/Balloon/.deps/BalloonSim.Po:
> /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \
> FDM/Balloon/.deps/BalloonSim.Po:/FlightGear/fgdev9.6/include/GL/gl.h:
> FDM/Balloon/.deps/BalloonSim.Po:/System/Library/Frameworks/
> OpenGL.framework/Headers/gl.h:
>
> Ouch! It turns out I have a GL directory in fgdev9.6/include that
> contains:
>
> /FlightGear/fgdev9.6/include] ima% ls -l Gl
> total 32
> -rwxrwxr-x 1 ima staff 232 14 Dec 2002 gl.h
> -rwxrwxr-x 1 ima staff 26 14 Dec 2002 glext.h
> -rwxrwxr-x 1 ima staff 24 14 Dec 2002 glu.h
> -rwxrwxr-x 1 ima staff 23 14 Dec 2002 glut.h
>
> Yes, they're nearly two years old! Maybe that's why I could build and
> you couldn't? 8-(
>
> The real headers are:
>
> [Four-Computer:frameworks/opengl.framework/headers] ima% ls -l gl*
> -rw-r--r-- 1 root wheel 124202 12 Sep 2003 gl.h
> -rw-r--r-- 1 root wheel 200923 12 Sep 2003 glext.h
> -rw-r--r-- 1 root wheel 294 12 Sep 2003 gliContext.h
> -rw-r--r-- 1 root wheel 47720 12 Sep 2003 gliDispatch.h
> -rw-r--r-- 1 root wheel 16259 12 Sep 2003 glu.h
> -rw-r--r-- 1 root wheel2597 12 Sep 2003 gluContext.h
> -rw-r--r-- 1 root wheel2242 12 Sep 2003 gluMacro.h
>
> The AGL headers are:
>
> ls -l /System/Library/Frameworks/AGL.framework/Versions/A/Headers
> total 248
> -rw-r--r-- 1 root wheel 16716 13 Sep 2003 agl.h
> -rw-r--r-- 1 root wheel889 13 Sep 2003 aglContext.h
> -rw-r--r-- 1 root wheel 71046 13 Sep 2003 aglMacro.h
> -rw-r--r-- 1 root wheel 1244 13 Sep 2003 aglRenderers.h
> lrwxr-xr-x 1 root wheel 56 25 Jan 2004 gl.h ->
> /System/Library/Frameworks/OpenGL.framework/Headers/gl.h
> lrwxr-xr-x 1 root wheel 64 25 Jan 2004 gliContext.h ->
> /System/Library/Frameworks/OpenGL.framework/Headers/gliContext.h
> lrwxr-xr-x 1 root wheel 65 25 Jan 2004 gliDispatch.h ->
> /System/Library/Frameworks/OpenGL.framework/Headers/gliDispatch.h
> -rw-r--r-- 1 root wheel 4327 13 Sep 2003 glm.h
> lrwxr-xr-x 1 root wheel 57 25 Jan 2004 glu.h ->
> /System/Library/Frameworks/OpenGL.framework/Headers/glu.h
>
> When I remove this GL directory in fgdev9.6/include and rebuild, I get:
>
> Making all in tests
> source='est-epsilon.c' object='est-epsilon.o' libtool=no \
> depfile='.deps/est-epsilon.Po' tmpdepfile='.deps/est-epsilon.TPo' \
> depmode=gcc3 /bin/sh ../depcomp \
> gcc -DHAVE_CONFIG_H -I. -I. -I../src/Include
> -I/Users/ima/Desktop/FlightGear/fgdev9.6/include -g -O2 -D_REENTRANT
> -c `test -f 'est-epsilon.c' || echo './'`est-epsilon.c
> est-epsilon.c:11:19: GL/glut.h: No such file or directory
> est-epsilon.c: In function `main':
> est-epsilon.c:15: error: `GLfloat' undeclared (first use in this
> function)
> est-epsilon.c:15: error: (Each undeclared identifier is reported only
> once
> est-epsilon.c:15: error: for each function it appears in.)
> est-epsilon.c:15: error: parse error before "a"
> est-epsilon.c:17: error: `a' undeclared (first use in this function)
> est-e
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur, I have built FlightGear on Mac OS X. After a LOT of trial and error building SimGear and FlightGear without the X11 SDK. Great! 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/*. I was really concerned why I could build without these Gl errors and you couldn't on mac os x so I did some research I have open GL headers in /System/Library/Frameworks/OpenGL.framework/Versions/A/Headers and /System/Library/Frameworks/AGL.framework/Versions/A/Headers If I do a 'grep -r "GL" * from ./src/flightgear/src, I get (among other things) FDM/.deps/MagicCarpet.Po: /FlightGear/fgdev9.6/include/GL/gl.h \ FDM/.deps/MagicCarpet.Po: /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \ FDM/.deps/MagicCarpet.Po:/FlightGear/fgdev9.6/include/GL/gl.h: FDM/.deps/MagicCarpet.Po:/System/Library/Frameworks/OpenGL.framework/ Headers/gl.h: FDM/.deps/UFO.Po: /FlightGear/fgdev9.6/include/GL/gl.h \ FDM/.deps/UFO.Po: /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \ FDM/.deps/UFO.Po:/FlightGear/fgdev9.6/include/GL/gl.h: FDM/.deps/UFO.Po:/System/Library/Frameworks/OpenGL.framework/Headers/ gl.h: FDM/Balloon/.deps/BalloonSim.Po: /FlightGear/fgdev9.6/include/GL/gl.h \ FDM/Balloon/.deps/BalloonSim.Po: /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \ FDM/Balloon/.deps/BalloonSim.Po:/FlightGear/fgdev9.6/include/GL/gl.h: FDM/Balloon/.deps/BalloonSim.Po:/System/Library/Frameworks/ OpenGL.framework/Headers/gl.h: Ouch! It turns out I have a GL directory in fgdev9.6/include that contains: /FlightGear/fgdev9.6/include] ima% ls -l Gl total 32 -rwxrwxr-x 1 ima staff 232 14 Dec 2002 gl.h -rwxrwxr-x 1 ima staff 26 14 Dec 2002 glext.h -rwxrwxr-x 1 ima staff 24 14 Dec 2002 glu.h -rwxrwxr-x 1 ima staff 23 14 Dec 2002 glut.h Yes, they're nearly two years old! Maybe that's why I could build and you couldn't? 8-( The real headers are: [Four-Computer:frameworks/opengl.framework/headers] ima% ls -l gl* -rw-r--r-- 1 root wheel 124202 12 Sep 2003 gl.h -rw-r--r-- 1 root wheel 200923 12 Sep 2003 glext.h -rw-r--r-- 1 root wheel 294 12 Sep 2003 gliContext.h -rw-r--r-- 1 root wheel 47720 12 Sep 2003 gliDispatch.h -rw-r--r-- 1 root wheel 16259 12 Sep 2003 glu.h -rw-r--r-- 1 root wheel2597 12 Sep 2003 gluContext.h -rw-r--r-- 1 root wheel2242 12 Sep 2003 gluMacro.h The AGL headers are: ls -l /System/Library/Frameworks/AGL.framework/Versions/A/Headers total 248 -rw-r--r-- 1 root wheel 16716 13 Sep 2003 agl.h -rw-r--r-- 1 root wheel889 13 Sep 2003 aglContext.h -rw-r--r-- 1 root wheel 71046 13 Sep 2003 aglMacro.h -rw-r--r-- 1 root wheel 1244 13 Sep 2003 aglRenderers.h lrwxr-xr-x 1 root wheel 56 25 Jan 2004 gl.h -> /System/Library/Frameworks/OpenGL.framework/Headers/gl.h lrwxr-xr-x 1 root wheel 64 25 Jan 2004 gliContext.h -> /System/Library/Frameworks/OpenGL.framework/Headers/gliContext.h lrwxr-xr-x 1 root wheel 65 25 Jan 2004 gliDispatch.h -> /System/Library/Frameworks/OpenGL.framework/Headers/gliDispatch.h -rw-r--r-- 1 root wheel 4327 13 Sep 2003 glm.h lrwxr-xr-x 1 root wheel 57 25 Jan 2004 glu.h -> /System/Library/Frameworks/OpenGL.framework/Headers/glu.h When I remove this GL directory in fgdev9.6/include and rebuild, I get: Making all in tests source='est-epsilon.c' object='est-epsilon.o' libtool=no \ depfile='.deps/est-epsilon.Po' tmpdepfile='.deps/est-epsilon.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../src/Include -I/Users/ima/Desktop/FlightGear/fgdev9.6/include -g -O2 -D_REENTRANT -c `test -f 'est-epsilon.c' || echo './'`est-epsilon.c est-epsilon.c:11:19: GL/glut.h: No such file or directory est-epsilon.c: In function `main': est-epsilon.c:15: error: `GLfloat' undeclared (first use in this function) est-epsilon.c:15: error: (Each undeclared identifier is reported only once est-epsilon.c:15: error: for each function it appears in.) est-epsilon.c:15: error: parse error before "a" est-epsilon.c:17: error: `a' undeclared (first use in this function) est-epsilon.c:22: error: `t' undeclared (first use in this function) make[1]: *** [est-epsilon.o] Error 1 make: *** [all-recursive] Error 1 Sound familiar? So yes, it sounds like your patch is something needed for mac os x, either that or symlinks in ./include/GL to point to the real headers 8-) Just kidding, the patch is a MUCH better idea. Chalk it up to apple having non-standard locations for the opengl header files. I don't know where I came up with the idea of creating a GL directory, but there you go, it's there so go figure... I guess I 'll be getting rid of it as soon as your patch is ready. 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 a
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
* 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 + (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 > > > sheee > > > 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 > > > > > -- > > -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
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 + (UTC) > > To: <[EMAIL PROTECTED]> > > > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > [EMAIL PROTECTED] wrote: > > > >> Do you thin
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Yes I found out quickly that locate does not stay up to date. But it did find everything. I think the datebase rebuilds daily or something. But I decided to try to build simgear again (from CVS) and it seems in a file called matlib.cxx in material it contains the following line: #include and it needs to be changed to #include in order to build on OSX. At least for me. Previously I had it using the X11 supplied GLUT headers but I didn't this time which is how I noticed this. It's the same story but a little different in clouds3d/glut_shapes.c line 54 #include shoud be #include Same thing in glut_shapes.h line 17 SkyMaterial.hpp in line 36 SkyCloud.cpp:36 I had to make the same two changes on many different files in order to get simgear to compile without using Apple's X11. I'll see if I can make a patch. I'll now try flightgear again. (I've already redone PLIB) On Sat, 13 Nov 2004 15:31:38 +0100, Boris Koenig <[EMAIL PROTECTED]> wrote: > Arthur Wiebe wrote: > > Another way to do it which is what I did was use the following command: > > locate plibfnt > > > > It returned: > > /fgfs/lib/libplibfnt.a > > /Users/myuser/FlightGear/plib/src/fnt/libplibfnt.a > > "(s)locate" doesn't really "browse" your file system, as 'find' would > do - rather, (s)locate runs a query against a simple database, > if that database is not in sync with your local file system, it can > very well happen, that (s)locate returns results that don't resemble > the actual situation on your hard disk, hence it is recommended that > you either use 'find' directly or simply run a 'updatedb' in order to > synchronize the database with your file system - which may take quite > a while, depending on your file system structure. > > Also, you won't have to do a manual search for any references of 'load', > you can easily use 'grep' for that, too - something like: > > nm library.a | grep -i font | grep -i load | less > > would return all results that contain a "font" AND a "load" > reference, limiting the search in such a manner would probably > also make the piping to less superfluous. > > Using some clever sed'ing could even take care of automatically > comparing object file exports and library exports. > > - > Boris > > ___ > > > 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur Wiebe wrote: Another way to do it which is what I did was use the following command: locate plibfnt It returned: /fgfs/lib/libplibfnt.a /Users/myuser/FlightGear/plib/src/fnt/libplibfnt.a "(s)locate" doesn't really "browse" your file system, as 'find' would do - rather, (s)locate runs a query against a simple database, if that database is not in sync with your local file system, it can very well happen, that (s)locate returns results that don't resemble the actual situation on your hard disk, hence it is recommended that you either use 'find' directly or simply run a 'updatedb' in order to synchronize the database with your file system - which may take quite a while, depending on your file system structure. Also, you won't have to do a manual search for any references of 'load', you can easily use 'grep' for that, too - something like: nm library.a | grep -i font | grep -i load | less would return all results that contain a "font" AND a "load" reference, limiting the search in such a manner would probably also make the piping to less superfluous. Using some clever sed'ing could even take care of automatically comparing object file exports and library exports. - Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Another way to do it which is what I did was use the following command:
locate plibfnt
It returned:
/fgfs/lib/libplibfnt.a
/Users/myuser/FlightGear/plib/src/fnt/libplibfnt.a
So no, unless the source file count I do not have another PLIB installation.
Even though I really have to work on my own projects, I'll try redoing
this PLIB thing.
On Fri, 12 Nov 2004 19:40:04 -0500, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Arthur,
>
> You've come so far, please don't give up now!
>
> >> This is the last day I'm going to work on this. If I can't get it to
> >> work today I will wait until Mac OS X 10.4 is released. (Tiger)
>
> Curt,
>
> Your command to find files works fine on Mac OS X.3.6, here's the
> result on my system:
>
> sudo find / -print | grep plibfnt
> Password:
> /FlightGear/fgdev9.6/lib/libplibfnt.a
> /FlightGear/fgdev9.6/src/plib/src/fnt/libplibfnt.a
>
> i.e. -- one built version, also copied to lib as the installed version
>
> Arthur,
>
> this is a plib issue. FlightGear is just the symptom. Have you tried
> any of the plib sample applications to see if your installed plib is in
> fact working? Just because something builds doesn't mean it works, I
> speak from unfortunate personal experience. 8-)
>
> Can anyone with plib developer authority possibly add these changes to
> plib/examples?
> They are required to build in Mac OS X
>
> Changes required to build plib examples on mac os x -- start
>
> --
> To use plib installed in a non-standard directory, I needed to set:
>
> setenv LDFLAGS -L/FlightGear/fgdev9.6/lib
> setenv CPPFLAGS -I/FlightGear/fgdev9.6/include
>
> (these are uppercase L (LDFLAGS) and uppercase I (CPPFLAGS), BTW)
>
> before running ./configure in the ./examples direction
>
> I then needed to modify js_demo_LDADD to add a few frameworks
>
> js_demo_LDADD = -lplibjs -lplibul -framework IOKit -framework
> CoreFoundation
>
> in the ./examples/src/js/makefile.
>
> I also needed to change ./examples/src/ssg/majik/makefile to add
> -framework IOKit -framework CoreFoundation to the end of
> majik_demo_LDADD giving
>
> majik_demo_LDADD = -lplibjs -lplibssg -lplibsg -lplibul $(GLUT_LIBS)
> $(OGL_LIBS) -framework IOKit -framework CoreFoundation
>
> I also needed to change ./examples/src/pw/makefile to add
> -framework IOKit -framework CoreFoundation -framework
> ApplicationServices -framework Carbon
>
> to pw_demo_LDFLAGS
>
> giving
>
> pw_demo_LDFLAGS = -framework IOKit -framework CoreFoundation -framework
> ApplicationServices -framework Carbon
>
> I added the same to pw_pui_LDFLAGS in the same file
>
> lorenz.cxx doesn't seem to exist and broke the build
>
> I created lorenz.cxx containing
>
> main()
> {
> }
>
> and rebuilt. No idea what this is.
>
> --
> Changes required to build plib examples on mac os x -- end
>
> Thanks!
>
> Ima
>
>
>
>
> ___
> 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
[Flightgear-devel] Re: FlightGear on Mac OS X
Er, I should have said make these changes for Mac OS X, as the plib/examples changes are only needed for the Mac OS X platform. Sorry for the confusion! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur,
You've come so far, please don't give up now!
This is the last day I'm going to work on this. If I can't get it to
work today I will wait until Mac OS X 10.4 is released. (Tiger)
Curt,
Your command to find files works fine on Mac OS X.3.6, here's the
result on my system:
sudo find / -print | grep plibfnt
Password:
/FlightGear/fgdev9.6/lib/libplibfnt.a
/FlightGear/fgdev9.6/src/plib/src/fnt/libplibfnt.a
i.e. -- one built version, also copied to lib as the installed version
Arthur,
this is a plib issue. FlightGear is just the symptom. Have you tried
any of the plib sample applications to see if your installed plib is in
fact working? Just because something builds doesn't mean it works, I
speak from unfortunate personal experience. 8-)
Can anyone with plib developer authority possibly add these changes to
plib/examples?
They are required to build in Mac OS X
Changes required to build plib examples on mac os x -- start
--
To use plib installed in a non-standard directory, I needed to set:
setenv LDFLAGS -L/FlightGear/fgdev9.6/lib
setenv CPPFLAGS -I/FlightGear/fgdev9.6/include
(these are uppercase L (LDFLAGS) and uppercase I (CPPFLAGS), BTW)
before running ./configure in the ./examples direction
I then needed to modify js_demo_LDADD to add a few frameworks
js_demo_LDADD = -lplibjs -lplibul -framework IOKit -framework
CoreFoundation
in the ./examples/src/js/makefile.
I also needed to change ./examples/src/ssg/majik/makefile to add
-framework IOKit -framework CoreFoundation to the end of
majik_demo_LDADD giving
majik_demo_LDADD = -lplibjs -lplibssg -lplibsg -lplibul $(GLUT_LIBS)
$(OGL_LIBS) -framework IOKit -framework CoreFoundation
I also needed to change ./examples/src/pw/makefile to add
-framework IOKit -framework CoreFoundation -framework
ApplicationServices -framework Carbon
to pw_demo_LDFLAGS
giving
pw_demo_LDFLAGS = -framework IOKit -framework CoreFoundation -framework
ApplicationServices -framework Carbon
I added the same to pw_pui_LDFLAGS in the same file
lorenz.cxx doesn't seem to exist and broke the build
I created lorenz.cxx containing
main()
{
}
and rebuilt. No idea what this is.
--
Changes required to build plib examples on mac os x -- end
Thanks!
Ima
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur Wiebe wrote: I actually had two different PLIB installations floating around. But only one in the prefix. But even after removing the other two I still get this error. Compilers will typically search a default path that usually/often includes /usr/include, /usr/lib, /usr/local/include, /usr/local/lib, and some usr/include tree specific to the compiler version. If you specify a prefix that simply appends additional search directories to the standard path. The next thing I would do, if you are sure you only have one copy of libplibfnt.a and are sure that was built with the same compiler version you are using to build flightgear is: run "nm libplibfnt.a | less" and search for instances of the string "load". Do the same thing for layout-test.o See if the munged names actually match. If they don't there could be some type promotion assumption in the header file that your compiler isn't doing ... you may have to do some sort of explicite cast to force your compiler to use the exact same parameter and return types so that the name munging comes out identical. You shouldn't have to do this though since others seem to be able to build successfully. My money is still on some sort of stray copy of libplibfnt floating around or a mismatch in compiler versions, or you still have pieces of plib or flightgear that never actually got rebuilt when switched compiler versions. Regards, Curt. On Fri, 12 Nov 2004 10:19:13 -0600, Curtis L. Olson <[EMAIL PROTECTED]> wrote: Arthur, The missing symbol should be in the -lplibfnt library. Do you perhaps have an older version of plib (or parts of it) built with a different compiler still floating around on your system? By default plib tries to install itself in /usr/lib and /usr/include, so I would check there first. If you don't find anything there, then I'd probably do a "find" from the top level ... something like: find / -print | grep plibfnt (Note that different version of find can have slightly different behavior nuances, so if the above command doesn't quite do anything useful, check your local man page for appropriate options.) See if that turns up something that is trying to hide from you. If the compiler is finding an outdated libplibfnt.a in it's search path before the correct one, then you could see this sort of error. If that doesn't turn anything up, then we'll have to search for some other cause. Regards, Curt. Arthur Wiebe wrote: I just started over again. Building PLIB, SimGear, and FlightGear all from CVS. PLIB and SimGear worked of course but flightgear halts when building the GUI: Making all in GUI if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT new_gui.o -MD -MP -MF ".deps/new_gui.Tpo" -c -o new_gui.o new_gui.cxx; \ then mv -f ".deps/new_gui.Tpo" ".deps/new_gui.Po"; else rm -f ".deps/new_gui.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT dialog.o -MD -MP -MF ".deps/dialog.Tpo" -c -o dialog.o dialog.cxx; \ then mv -f ".deps/dialog.Tpo" ".deps/dialog.Po"; else rm -f ".deps/dialog.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT menubar.o -MD -MP -MF ".deps/menubar.Tpo" -c -o menubar.o menubar.cxx; \ then mv -f ".deps/menubar.Tpo" ".deps/menubar.Po"; else rm -f ".deps/menubar.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui.o -MD -MP -MF ".deps/gui.Tpo" -c -o gui.o gui.cxx; \ then mv -f ".deps/gui.Tpo" ".deps/gui.Po"; else rm -f ".deps/gui.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_funcs.o -MD -MP -MF ".deps/gui_funcs.Tpo" -c -o gui_funcs.o gui_funcs.cxx; \ then mv -f ".deps/gui_funcs.Tpo" ".deps/gui_funcs.Po"; else rm -f ".deps/gui_funcs.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_local.o -MD -MP -MF ".deps/gui_local.Tpo" -c -o gui_local.o gui_local.cxx; \ then mv -f ".deps/gui_local.Tpo" ".deps/gui_local.Po"; else rm -f ".deps/gui_local.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT mouse.o -MD -MP -MF ".deps/mouse.Tpo" -c -o mouse.o mouse.cxx; \ then mv -f ".deps/mouse.Tpo" ".deps/mouse.Po"; else rm -f ".deps/mouse.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT preset_dlg.o -MD -MP -MF ".deps/preset_dlg.Tpo" -c -o preset_dlg.o preset_dlg.cxx; \ then mv -f ".deps/preset_dlg.Tpo" ".deps/preset_dlg.Po"; else rm -f ".deps/preset_dlg.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
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 + (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 > sheee > 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
I actually had two different PLIB installations floating around. But only one in the prefix. But even after removing the other two I still get this error. On Fri, 12 Nov 2004 10:19:13 -0600, Curtis L. Olson <[EMAIL PROTECTED]> wrote: > Arthur, > > The missing symbol should be in the -lplibfnt library. Do you perhaps > have an older version of plib (or parts of it) built with a different > compiler still floating around on your system? > > By default plib tries to install itself in /usr/lib and /usr/include, so > I would check there first. If you don't find anything there, then I'd > probably do a "find" from the top level ... something like: > > find / -print | grep plibfnt > > (Note that different version of find can have slightly different > behavior nuances, so if the above command doesn't quite do anything > useful, check your local man page for appropriate options.) > > See if that turns up something that is trying to hide from you. If the > compiler is finding an outdated libplibfnt.a in it's search path before > the correct one, then you could see this sort of error. If that doesn't > turn anything up, then we'll have to search for some other cause. > > Regards, > > Curt. > > > > > Arthur Wiebe wrote: > > >I just started over again. Building PLIB, SimGear, and FlightGear all from > >CVS. > > > >PLIB and SimGear worked of course but flightgear halts when building the GUI: > > > >Making all in GUI > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT new_gui.o -MD > >-MP -MF ".deps/new_gui.Tpo" -c -o new_gui.o new_gui.cxx; \ > >then mv -f ".deps/new_gui.Tpo" ".deps/new_gui.Po"; else rm -f > >".deps/new_gui.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT dialog.o -MD > >-MP -MF ".deps/dialog.Tpo" -c -o dialog.o dialog.cxx; \ > >then mv -f ".deps/dialog.Tpo" ".deps/dialog.Po"; else rm -f > >".deps/dialog.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT menubar.o -MD > >-MP -MF ".deps/menubar.Tpo" -c -o menubar.o menubar.cxx; \ > >then mv -f ".deps/menubar.Tpo" ".deps/menubar.Po"; else rm -f > >".deps/menubar.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui.o -MD -MP > >-MF ".deps/gui.Tpo" -c -o gui.o gui.cxx; \ > >then mv -f ".deps/gui.Tpo" ".deps/gui.Po"; else rm -f ".deps/gui.Tpo"; > >exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_funcs.o > >-MD -MP -MF ".deps/gui_funcs.Tpo" -c -o gui_funcs.o gui_funcs.cxx; \ > >then mv -f ".deps/gui_funcs.Tpo" ".deps/gui_funcs.Po"; else rm -f > >".deps/gui_funcs.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_local.o > >-MD -MP -MF ".deps/gui_local.Tpo" -c -o gui_local.o gui_local.cxx; \ > >then mv -f ".deps/gui_local.Tpo" ".deps/gui_local.Po"; else rm -f > >".deps/gui_local.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT mouse.o -MD > >-MP -MF ".deps/mouse.Tpo" -c -o mouse.o mouse.cxx; \ > >then mv -f ".deps/mouse.Tpo" ".deps/mouse.Po"; else rm -f > >".deps/mouse.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT preset_dlg.o > >-MD -MP -MF ".deps/preset_dlg.Tpo" -c -o preset_dlg.o preset_dlg.cxx; > >\ > >then mv -f ".deps/preset_dlg.Tpo" ".deps/preset_dlg.Po"; else rm -f > >".deps/preset_dlg.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT prop_picker.o > >-MD -MP -MF ".deps/prop_picker.Tpo" -c -o prop_picker.o > >prop_picker.cxx; \ > >then mv -f ".deps/prop_picker.Tpo" ".deps/prop_picker.Po"; else rm -f > >".deps/prop_picker.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT sgVec3Slider.o > >-MD -MP -MF ".deps/sgVec3Slider.Tpo" -c -o sgVec3Slider.o > >sgVec3Slider.cxx; \ > >then mv -f ".deps/sgVec3Slider.Tpo" ".deps/sgVec3Slider.Po"; else rm > >-f ".deps/sgVec3Slider.Tpo"; exit 1; fi > >if gcc -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT trackball.o > >-MD -MP -MF ".deps/trackball.Tpo" -c -o trackball.o trackball.c; \ > >then mv -f ".deps/trackball.Tpo" ".deps/trackball.Po"; else rm -f > >".deps/trackball.Tpo"; exit 1; fi > >if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../.
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur, The missing symbol should be in the -lplibfnt library. Do you perhaps have an older version of plib (or parts of it) built with a different compiler still floating around on your system? By default plib tries to install itself in /usr/lib and /usr/include, so I would check there first. If you don't find anything there, then I'd probably do a "find" from the top level ... something like: find / -print | grep plibfnt (Note that different version of find can have slightly different behavior nuances, so if the above command doesn't quite do anything useful, check your local man page for appropriate options.) See if that turns up something that is trying to hide from you. If the compiler is finding an outdated libplibfnt.a in it's search path before the correct one, then you could see this sort of error. If that doesn't turn anything up, then we'll have to search for some other cause. Regards, Curt. Arthur Wiebe wrote: I just started over again. Building PLIB, SimGear, and FlightGear all from CVS. PLIB and SimGear worked of course but flightgear halts when building the GUI: Making all in GUI if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT new_gui.o -MD -MP -MF ".deps/new_gui.Tpo" -c -o new_gui.o new_gui.cxx; \ then mv -f ".deps/new_gui.Tpo" ".deps/new_gui.Po"; else rm -f ".deps/new_gui.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT dialog.o -MD -MP -MF ".deps/dialog.Tpo" -c -o dialog.o dialog.cxx; \ then mv -f ".deps/dialog.Tpo" ".deps/dialog.Po"; else rm -f ".deps/dialog.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT menubar.o -MD -MP -MF ".deps/menubar.Tpo" -c -o menubar.o menubar.cxx; \ then mv -f ".deps/menubar.Tpo" ".deps/menubar.Po"; else rm -f ".deps/menubar.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui.o -MD -MP -MF ".deps/gui.Tpo" -c -o gui.o gui.cxx; \ then mv -f ".deps/gui.Tpo" ".deps/gui.Po"; else rm -f ".deps/gui.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_funcs.o -MD -MP -MF ".deps/gui_funcs.Tpo" -c -o gui_funcs.o gui_funcs.cxx; \ then mv -f ".deps/gui_funcs.Tpo" ".deps/gui_funcs.Po"; else rm -f ".deps/gui_funcs.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_local.o -MD -MP -MF ".deps/gui_local.Tpo" -c -o gui_local.o gui_local.cxx; \ then mv -f ".deps/gui_local.Tpo" ".deps/gui_local.Po"; else rm -f ".deps/gui_local.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT mouse.o -MD -MP -MF ".deps/mouse.Tpo" -c -o mouse.o mouse.cxx; \ then mv -f ".deps/mouse.Tpo" ".deps/mouse.Po"; else rm -f ".deps/mouse.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT preset_dlg.o -MD -MP -MF ".deps/preset_dlg.Tpo" -c -o preset_dlg.o preset_dlg.cxx; \ then mv -f ".deps/preset_dlg.Tpo" ".deps/preset_dlg.Po"; else rm -f ".deps/preset_dlg.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT prop_picker.o -MD -MP -MF ".deps/prop_picker.Tpo" -c -o prop_picker.o prop_picker.cxx; \ then mv -f ".deps/prop_picker.Tpo" ".deps/prop_picker.Po"; else rm -f ".deps/prop_picker.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT sgVec3Slider.o -MD -MP -MF ".deps/sgVec3Slider.Tpo" -c -o sgVec3Slider.o sgVec3Slider.cxx; \ then mv -f ".deps/sgVec3Slider.Tpo" ".deps/sgVec3Slider.Po"; else rm -f ".deps/sgVec3Slider.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT trackball.o -MD -MP -MF ".deps/trackball.Tpo" -c -o trackball.o trackball.c; \ then mv -f ".deps/trackball.Tpo" ".deps/trackball.Po"; else rm -f ".deps/trackball.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT puList.o -MD -MP -MF ".deps/puList.Tpo" -c -o puList.o puList.cxx; \ then mv -f ".deps/puList.Tpo" ".deps/puList.Po"; else rm -f ".deps/puList.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT AirportList.o -MD -MP -MF ".deps/AirportList.Tpo" -c -o AirportList.o AirportList.cxx; \ then mv -f ".deps/AirportList.Tpo" ".deps/AirportList.Po"; else rm
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
I just started over again. Building PLIB, SimGear, and FlightGear all from CVS. PLIB and SimGear worked of course but flightgear halts when building the GUI: Making all in GUI if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT new_gui.o -MD -MP -MF ".deps/new_gui.Tpo" -c -o new_gui.o new_gui.cxx; \ then mv -f ".deps/new_gui.Tpo" ".deps/new_gui.Po"; else rm -f ".deps/new_gui.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT dialog.o -MD -MP -MF ".deps/dialog.Tpo" -c -o dialog.o dialog.cxx; \ then mv -f ".deps/dialog.Tpo" ".deps/dialog.Po"; else rm -f ".deps/dialog.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT menubar.o -MD -MP -MF ".deps/menubar.Tpo" -c -o menubar.o menubar.cxx; \ then mv -f ".deps/menubar.Tpo" ".deps/menubar.Po"; else rm -f ".deps/menubar.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui.o -MD -MP -MF ".deps/gui.Tpo" -c -o gui.o gui.cxx; \ then mv -f ".deps/gui.Tpo" ".deps/gui.Po"; else rm -f ".deps/gui.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_funcs.o -MD -MP -MF ".deps/gui_funcs.Tpo" -c -o gui_funcs.o gui_funcs.cxx; \ then mv -f ".deps/gui_funcs.Tpo" ".deps/gui_funcs.Po"; else rm -f ".deps/gui_funcs.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT gui_local.o -MD -MP -MF ".deps/gui_local.Tpo" -c -o gui_local.o gui_local.cxx; \ then mv -f ".deps/gui_local.Tpo" ".deps/gui_local.Po"; else rm -f ".deps/gui_local.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT mouse.o -MD -MP -MF ".deps/mouse.Tpo" -c -o mouse.o mouse.cxx; \ then mv -f ".deps/mouse.Tpo" ".deps/mouse.Po"; else rm -f ".deps/mouse.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT preset_dlg.o -MD -MP -MF ".deps/preset_dlg.Tpo" -c -o preset_dlg.o preset_dlg.cxx; \ then mv -f ".deps/preset_dlg.Tpo" ".deps/preset_dlg.Po"; else rm -f ".deps/preset_dlg.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT prop_picker.o -MD -MP -MF ".deps/prop_picker.Tpo" -c -o prop_picker.o prop_picker.cxx; \ then mv -f ".deps/prop_picker.Tpo" ".deps/prop_picker.Po"; else rm -f ".deps/prop_picker.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT sgVec3Slider.o -MD -MP -MF ".deps/sgVec3Slider.Tpo" -c -o sgVec3Slider.o sgVec3Slider.cxx; \ then mv -f ".deps/sgVec3Slider.Tpo" ".deps/sgVec3Slider.Po"; else rm -f ".deps/sgVec3Slider.Tpo"; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT trackball.o -MD -MP -MF ".deps/trackball.Tpo" -c -o trackball.o trackball.c; \ then mv -f ".deps/trackball.Tpo" ".deps/trackball.Po"; else rm -f ".deps/trackball.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT puList.o -MD -MP -MF ".deps/puList.Tpo" -c -o puList.o puList.cxx; \ then mv -f ".deps/puList.Tpo" ".deps/puList.Po"; else rm -f ".deps/puList.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT AirportList.o -MD -MP -MF ".deps/AirportList.Tpo" -c -o AirportList.o AirportList.cxx; \ then mv -f ".deps/AirportList.Tpo" ".deps/AirportList.Po"; else rm -f ".deps/AirportList.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout.o -MD -MP -MF ".deps/layout.Tpo" -c -o layout.o layout.cxx; \ then mv -f ".deps/layout.Tpo" ".deps/layout.Po"; else rm -f ".deps/layout.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout-props.o -MD -MP -MF ".deps/layout-props.Tpo" -c -o layout-props.o layout-props.cxx; \ then mv -f ".deps/layout-props.Tpo" ".deps/layout-props.Po"; else rm -f ".deps/layout-props.Tpo"; exit 1; fi rm -f libGUI.a ar cru libGUI.a new_gui.o dialog.o menubar.o gui.o gui_funcs.o gui_local.o mouse.o preset_dlg.o prop_picker.o sgVec3Slider.o trackball.o puList.o AirportList.o layout.o layout-props.o ranlib libGUI.a if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Great to hear you got it! But I'm still having problems and I have been using "make clean" all the time. Don't think that'll help for my situation. On Thu, 11 Nov 2004 18:11:53 -0600, Curtis L. Olson <[EMAIL PROTECTED]> wrote: > Adam Dershowitz wrote: > > > > >I finally got it all to build and work! > > > >Curt, you were correct, despite what I said below. Seems that when I > >rebuilt everything, it was not actually everything. I somehow missed a few > >things. I think that the specific problem was that clouds3d is one > >directory deeper than most other things, and I believe that I just did not > >clear out the object files, or the library, that was there before I redid > >the build. So it was trying to link against the version of that one library > >that I had built with 2.95.2. > > > > > > For those that are new to the unix style build system (and I don't mean > to imply that you might be if you aren't) but you can run "make clean" > in the top level source directory to clean out all the built object > files, libs, and executables. This is usually a bit safer (and easier) > than trying to find and remove them all by hand. > > >Once I cleared that up, it seems that it all did build as advertised, except > >that I did do those couple of patches to plib. But Arthur says that using > >the CVS instead of the download of that will make that problem go away as > >well. I should try that. > > > >Thanks for all of the help and suggestions. > >FlightGear is a great program! > > > > > > Cool, glad to hear you are up and running! > > > > Curt. > > -- > Curtis Olsonhttp://www.flightgear.org/~curt > HumanFIRST Program http://www.humanfirst.umn.edu/ > FlightGear Project http://www.flightgear.org > Unique text:2f585eeea02e2c79d7b1d8c4963bae2d > > ___ > 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Adam Dershowitz wrote: I finally got it all to build and work! Curt, you were correct, despite what I said below. Seems that when I rebuilt everything, it was not actually everything. I somehow missed a few things. I think that the specific problem was that clouds3d is one directory deeper than most other things, and I believe that I just did not clear out the object files, or the library, that was there before I redid the build. So it was trying to link against the version of that one library that I had built with 2.95.2. For those that are new to the unix style build system (and I don't mean to imply that you might be if you aren't) but you can run "make clean" in the top level source directory to clean out all the built object files, libs, and executables. This is usually a bit safer (and easier) than trying to find and remove them all by hand. Once I cleared that up, it seems that it all did build as advertised, except that I did do those couple of patches to plib. But Arthur says that using the CVS instead of the download of that will make that problem go away as well. I should try that. Thanks for all of the help and suggestions. FlightGear is a great program! Cool, glad to hear you are up and running! Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
I finally got it all to build and work! Curt, you were correct, despite what I said below. Seems that when I rebuilt everything, it was not actually everything. I somehow missed a few things. I think that the specific problem was that clouds3d is one directory deeper than most other things, and I believe that I just did not clear out the object files, or the library, that was there before I redid the build. So it was trying to link against the version of that one library that I had built with 2.95.2. Once I cleared that up, it seems that it all did build as advertised, except that I did do those couple of patches to plib. But Arthur says that using the CVS instead of the download of that will make that problem go away as well. I should try that. Thanks for all of the help and suggestions. FlightGear is a great program! -- Adam > From: Adam Dershowitz <[EMAIL PROTECTED]> > Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> > Date: Thu, 11 Nov 2004 11:25:14 -0800 > To: FlightGear developers discussions <[EMAIL PROTECTED]> > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > >> From: "Curtis L. Olson" <[EMAIL PROTECTED]> >> Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> >> Date: Thu, 11 Nov 2004 13:09:21 -0600 >> To: FlightGear developers discussions <[EMAIL PROTECTED]> >> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X >> >> Adam Dershowitz wrote: >> >>> >>> >>>> From: Arthur Wiebe <[EMAIL PROTECTED]> >>>> Reply-To: FlightGear developers discussions >>>> <[EMAIL PROTECTED]> >>>> Date: Thu, 11 Nov 2004 13:41:58 -0500 >>>> To: FlightGear developers discussions <[EMAIL PROTECTED]> >>>> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X >>>> >>>> After setting two environment variables I was able to get simgear >>>> 0.3.7 to compile without any problems. >>>> >>>> In bash you would set them like this: >>>> export CFLAGS=-I/usr/X11R6/include >>>> export CXXFLAGS=-I/usr/X11R6/include >>>> >>>> And I built plib 1.8.3 with help from the diffs you sent but building >>>> from CVS worked for me without any patching. >>>> >>>> >>> >>> I guess that means that the appropriate patches are already in the plib CVS, >>> just not yet released. >>> >>> >>> >>>> Now FlightGear itself is another story. I had to upgrade automake in >>>> order to run the autogen.sh script successfully. >>>> >>>> >>> >>> That is very strange, because I did not have to. I wonder what is different >>> about our setups? >>> >>> >>> >>> >>>> I have not yet got FlightGear 0.9.6 to compile. Keep on getting: >>>> >>>> -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL >>>> -framework Carbon -lobjc >>>> ld: Undefined symbols: >>>> fntTexFont::load(char const*, unsigned int, unsigned int) >>>> make[2]: *** [layout-test] Error 1 >>>> make[1]: *** [all-recursive] Error 1 >>>> make: *** [all-recursive] Error 1 >>>> >>>> >>> >>> What is also strange is that I can get FG to compile, up to the final link >>> stage. I think that is the same problem that you are having, but we are >>> getting different Undefined symbols. Mine seem to be from stuff that I have >>> already built (plib). >>> >>> >> >> Did you build plib with the same version of the compiler you are using >> to build everything else? Different compilers (and compiler versions) >> can do the c++ name munging differently which can result in undefined >> symbols at link time. At compile time, the compiler just reads the >> .h, but at link time it tries to match up requested functions with >> anything in any of the specified libraries. But if the library is >> compiled with a different version of the compiler, the requested symbol >> might not match the published symbols in the library and so things end >> up not being resolved at the link phase. >> >> Curt. >> >> -- >> Curtis Olsonhttp://www.flightgear.org/~curt >> HumanFIRST Program http://www.humanfirst.umn.edu/ >> FlightGear Project http://www.flightgear.org >> Unique text:2f585eeea02e2c79d7b1d8c4963bae2d >> >> >> ___ >> Flightgear-devel mailing list >> [EMAIL PROTECTED] >> http://mail.flightgear.org/mailman/listinfo/flightgear-devel >> 2f585eeea02e2c79d7b1d8c4963bae2d > > Yup, all built with gcc 3.3. > Early on I followed the users guide which says that 2.95 is required. But I > delete all of my object code and libraries, then rebuilt. > > > > > ___ > 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur Wiebe wrote: > I built PLIB and SimGear with automake 1.6.3 instead of 1.9.3 but I > don't think that would be a problem. I believe you won't need to deal with 'automake' as long as you stick to the source code 'release' packages, because 'configure' is already there. 'automake' comes into play when you intend to build the CVS tree, 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
I wouldn't mind at all helping with updating the docs. I have some experience with my own projects. Keeping the documentation up to date is harder than writing code :) By the way I have the same problem trying to build FlightGear from CVS as the 0.9.6 release. PLIB, simgear, and almost flightgear all built with GCC 3.3 but it still doesn't work. I built PLIB and SimGear with automake 1.6.3 instead of 1.9.3 but I don't think that would be a problem. On Thu, 11 Nov 2004 22:00:48 + (UTC), Martin Spott <[EMAIL PROTECTED]> wrote: > [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 > sheee > 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
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 sheee 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
> From: "Curtis L. Olson" <[EMAIL PROTECTED]> > Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> > Date: Thu, 11 Nov 2004 13:09:21 -0600 > To: FlightGear developers discussions <[EMAIL PROTECTED]> > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > Adam Dershowitz wrote: > >> >> >>> From: Arthur Wiebe <[EMAIL PROTECTED]> >>> Reply-To: FlightGear developers discussions >>> <[EMAIL PROTECTED]> >>> Date: Thu, 11 Nov 2004 13:41:58 -0500 >>> To: FlightGear developers discussions <[EMAIL PROTECTED]> >>> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X >>> >>> After setting two environment variables I was able to get simgear >>> 0.3.7 to compile without any problems. >>> >>> In bash you would set them like this: >>> export CFLAGS=-I/usr/X11R6/include >>> export CXXFLAGS=-I/usr/X11R6/include >>> >>> And I built plib 1.8.3 with help from the diffs you sent but building >>> from CVS worked for me without any patching. >>> >>> >> >> I guess that means that the appropriate patches are already in the plib CVS, >> just not yet released. >> >> >> >>> Now FlightGear itself is another story. I had to upgrade automake in >>> order to run the autogen.sh script successfully. >>> >>> >> >> That is very strange, because I did not have to. I wonder what is different >> about our setups? >> >> >> >> >>> I have not yet got FlightGear 0.9.6 to compile. Keep on getting: >>> >>> -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL >>> -framework Carbon -lobjc >>> ld: Undefined symbols: >>> fntTexFont::load(char const*, unsigned int, unsigned int) >>> make[2]: *** [layout-test] Error 1 >>> make[1]: *** [all-recursive] Error 1 >>> make: *** [all-recursive] Error 1 >>> >>> >> >> What is also strange is that I can get FG to compile, up to the final link >> stage. I think that is the same problem that you are having, but we are >> getting different Undefined symbols. Mine seem to be from stuff that I have >> already built (plib). >> >> > > Did you build plib with the same version of the compiler you are using > to build everything else? Different compilers (and compiler versions) > can do the c++ name munging differently which can result in undefined > symbols at link time. At compile time, the compiler just reads the > .h, but at link time it tries to match up requested functions with > anything in any of the specified libraries. But if the library is > compiled with a different version of the compiler, the requested symbol > might not match the published symbols in the library and so things end > up not being resolved at the link phase. > > Curt. > > -- > Curtis Olsonhttp://www.flightgear.org/~curt > HumanFIRST Program http://www.humanfirst.umn.edu/ > FlightGear Project http://www.flightgear.org > Unique text:2f585eeea02e2c79d7b1d8c4963bae2d > > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d Yup, all built with gcc 3.3. Early on I followed the users guide which says that 2.95 is required. But I delete all of my object code and libraries, then rebuilt. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Just a quick note as I am catching up on all this: Arthur Wiebe wrote: Now FlightGear itself is another story. I had to upgrade automake in order to run the autogen.sh script successfully. While I wouldn't consider this to be a very common problem, it would probably not be a bad idea to add a simple version check to the autogen script, something like `autoconf --version | grep $REQUIRED_VERSION` That way one could at least display a remark whenever the autotools package doesn't match the required version. But I am really not sure how many other people have had problems because of the autotools being out dated. Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Adam Dershowitz wrote: From: Arthur Wiebe <[EMAIL PROTECTED]> Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> Date: Thu, 11 Nov 2004 13:41:58 -0500 To: FlightGear developers discussions <[EMAIL PROTECTED]> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X After setting two environment variables I was able to get simgear 0.3.7 to compile without any problems. In bash you would set them like this: export CFLAGS=-I/usr/X11R6/include export CXXFLAGS=-I/usr/X11R6/include And I built plib 1.8.3 with help from the diffs you sent but building from CVS worked for me without any patching. I guess that means that the appropriate patches are already in the plib CVS, just not yet released. Now FlightGear itself is another story. I had to upgrade automake in order to run the autogen.sh script successfully. That is very strange, because I did not have to. I wonder what is different about our setups? I have not yet got FlightGear 0.9.6 to compile. Keep on getting: -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 What is also strange is that I can get FG to compile, up to the final link stage. I think that is the same problem that you are having, but we are getting different Undefined symbols. Mine seem to be from stuff that I have already built (plib). Did you build plib with the same version of the compiler you are using to build everything else? Different compilers (and compiler versions) can do the c++ name munging differently which can result in undefined symbols at link time. At compile time, the compiler just reads the .h, but at link time it tries to match up requested functions with anything in any of the specified libraries. But if the library is compiled with a different version of the compiler, the requested symbol might not match the published symbols in the library and so things end up not being resolved at the link phase. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
> From: Arthur Wiebe <[EMAIL PROTECTED]> > Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> > Date: Thu, 11 Nov 2004 13:41:58 -0500 > To: FlightGear developers discussions <[EMAIL PROTECTED]> > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > After setting two environment variables I was able to get simgear > 0.3.7 to compile without any problems. > > In bash you would set them like this: > export CFLAGS=-I/usr/X11R6/include > export CXXFLAGS=-I/usr/X11R6/include > > And I built plib 1.8.3 with help from the diffs you sent but building > from CVS worked for me without any patching. I guess that means that the appropriate patches are already in the plib CVS, just not yet released. > > Now FlightGear itself is another story. I had to upgrade automake in > order to run the autogen.sh script successfully. That is very strange, because I did not have to. I wonder what is different about our setups? > > I have not yet got FlightGear 0.9.6 to compile. Keep on getting: > > -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL > -framework Carbon -lobjc > ld: Undefined symbols: > fntTexFont::load(char const*, unsigned int, unsigned int) > make[2]: *** [layout-test] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 What is also strange is that I can get FG to compile, up to the final link stage. I think that is the same problem that you are having, but we are getting different Undefined symbols. Mine seem to be from stuff that I have already built (plib). > > I will now try to get FlightGear from CVS to build. Not that I think > it will work. > > On Thu, 11 Nov 2004 10:24:45 -0800, Adam Dershowitz > <[EMAIL PROTECTED]> wrote: >> And were you able to get it all to build fine without any patches? >> As I said in the other Mac OS X thread, I had to make a few changes to get >> plib and SimGear to compile. >> And then I got it all to compile but the final link of FlightGear fails with >> some undefined symbols. These are things that should be in the library >> files that were already built. >> >> I am using gcc 3.3, automake 1.6.3 and autoconf 2.53 (these are the >> standards that are included with Xcode 1.5). And all fresh CVS code. >> >> -- Adam >> >>> From: <[EMAIL PROTECTED]> >>> Reply-To: FlightGear developers discussions >>> <[EMAIL PROTECTED]> >>> Date: Thu, 11 Nov 2004 12:22:52 -0500 >>> To: <[EMAIL PROTECTED]> >>> Subject: [Flightgear-devel] Re: FlightGear on Mac OS X >> >> >>> >>> Arthur, >>> >>> Makefile.in isn't in CVS. It is generated by automake. >>> >>> GNU Automake - http://www.gnu.org/software/automake >>> Freeware - Generates makefile.in files from makefile.am input files, >>> as part of the official GNU coding standards and build process. >>> Requires GNU autoconf. >>> On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] >>> wrote: >>> >>> are you running ./autogen.sh without an errors? Have you updated >>> aclocal and autoconf also? >>> >>> I just did a make clean and a plib build from cvs and it worked fine >>> under Mac os X (10.6). The rest of the build went ok also (simgear and >>> flightgear) though I had a modified (flightgear) Input/input.cxx and >>> Main/options.cxx. The FlightGear changes are for debugging some things >>> I was looking at at one time... >>> >>> I'm doing a 'make clean install' for SimGear and FlightGear now from >>> latest (1700 GMT) cvs. My plib and simgear are straight from cvs, >>> flightgear and data are straight from cvs (no modified local copies, >>> except for the FlightGear input.cxx and options.cxx files that I >>> mentioned above). >>> >>> Ima >>> >>>> >>>> Message: 8 >>>> Date: Thu, 11 Nov 2004 09:51:09 -0500 >>>> From: Arthur Wiebe <[EMAIL PROTECTED]> >>>> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X >>>> To: FlightGear developers discussions >>>> <[EMAIL PROTECTED]> >>>> Message-ID: <[EMAIL PROTECTED]> >>>> Content-Type: text/plain; charset=US-ASCII >>>> >>>> Since I was getting nowhere trying to build FG 0.9.6 I checked it out >>>> from CVS instead. After getting automake 1.9.3 I was able to run >>>> autogen.sh and configure but it seems Makefile.in is missing in CVS. >>>> >>>> configure:
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
After setting two environment variables I was able to get simgear 0.3.7 to compile without any problems. In bash you would set them like this: export CFLAGS=-I/usr/X11R6/include export CXXFLAGS=-I/usr/X11R6/include And I built plib 1.8.3 with help from the diffs you sent but building from CVS worked for me without any patching. Now FlightGear itself is another story. I had to upgrade automake in order to run the autogen.sh script successfully. I have not yet got FlightGear 0.9.6 to compile. Keep on getting: -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 I will now try to get FlightGear from CVS to build. Not that I think it will work. On Thu, 11 Nov 2004 10:24:45 -0800, Adam Dershowitz <[EMAIL PROTECTED]> wrote: > And were you able to get it all to build fine without any patches? > As I said in the other Mac OS X thread, I had to make a few changes to get > plib and SimGear to compile. > And then I got it all to compile but the final link of FlightGear fails with > some undefined symbols. These are things that should be in the library > files that were already built. > > I am using gcc 3.3, automake 1.6.3 and autoconf 2.53 (these are the > standards that are included with Xcode 1.5). And all fresh CVS code. > > -- Adam > > > From: <[EMAIL PROTECTED]> > > Reply-To: FlightGear developers discussions > > <[EMAIL PROTECTED]> > > Date: Thu, 11 Nov 2004 12:22:52 -0500 > > To: <[EMAIL PROTECTED]> > > Subject: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > > > Arthur, > > > > Makefile.in isn't in CVS. It is generated by automake. > > > > GNU Automake - http://www.gnu.org/software/automake > > Freeware - Generates makefile.in files from makefile.am input files, > > as part of the official GNU coding standards and build process. > > Requires GNU autoconf. > > On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] > > wrote: > > > > are you running ./autogen.sh without an errors? Have you updated > > aclocal and autoconf also? > > > > I just did a make clean and a plib build from cvs and it worked fine > > under Mac os X (10.6). The rest of the build went ok also (simgear and > > flightgear) though I had a modified (flightgear) Input/input.cxx and > > Main/options.cxx. The FlightGear changes are for debugging some things > > I was looking at at one time... > > > > I'm doing a 'make clean install' for SimGear and FlightGear now from > > latest (1700 GMT) cvs. My plib and simgear are straight from cvs, > > flightgear and data are straight from cvs (no modified local copies, > > except for the FlightGear input.cxx and options.cxx files that I > > mentioned above). > > > > Ima > > > >> > >> Message: 8 > >> Date: Thu, 11 Nov 2004 09:51:09 -0500 > >> From: Arthur Wiebe <[EMAIL PROTECTED]> > >> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > >> To: FlightGear developers discussions > >> <[EMAIL PROTECTED]> > >> Message-ID: <[EMAIL PROTECTED]> > >> Content-Type: text/plain; charset=US-ASCII > >> > >> Since I was getting nowhere trying to build FG 0.9.6 I checked it out > >> from CVS instead. After getting automake 1.9.3 I was able to run > >> autogen.sh and configure but it seems Makefile.in is missing in CVS. > >> > >> configure: creating ./config.status > >> config.status: creating Makefile > >> config.status: error: cannot find input file: Makefile.in > >> > >> That seems hard to believe though although it's true. I have no > >> Makefile.in. > > > > > > ___ > > 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 > -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
And were you able to get it all to build fine without any patches? As I said in the other Mac OS X thread, I had to make a few changes to get plib and SimGear to compile. And then I got it all to compile but the final link of FlightGear fails with some undefined symbols. These are things that should be in the library files that were already built. I am using gcc 3.3, automake 1.6.3 and autoconf 2.53 (these are the standards that are included with Xcode 1.5). And all fresh CVS code. -- Adam > From: <[EMAIL PROTECTED]> > Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> > Date: Thu, 11 Nov 2004 12:22:52 -0500 > To: <[EMAIL PROTECTED]> > Subject: [Flightgear-devel] Re: FlightGear on Mac OS X > > Arthur, > > Makefile.in isn't in CVS. It is generated by automake. > > GNU Automake - http://www.gnu.org/software/automake > Freeware - Generates makefile.in files from makefile.am input files, > as part of the official GNU coding standards and build process. > Requires GNU autoconf. > On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] > wrote: > > are you running ./autogen.sh without an errors? Have you updated > aclocal and autoconf also? > > I just did a make clean and a plib build from cvs and it worked fine > under Mac os X (10.6). The rest of the build went ok also (simgear and > flightgear) though I had a modified (flightgear) Input/input.cxx and > Main/options.cxx. The FlightGear changes are for debugging some things > I was looking at at one time... > > I'm doing a 'make clean install' for SimGear and FlightGear now from > latest (1700 GMT) cvs. My plib and simgear are straight from cvs, > flightgear and data are straight from cvs (no modified local copies, > except for the FlightGear input.cxx and options.cxx files that I > mentioned above). > > Ima > >> >> Message: 8 >> Date: Thu, 11 Nov 2004 09:51:09 -0500 >> From: Arthur Wiebe <[EMAIL PROTECTED]> >> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X >> To: FlightGear developers discussions >> <[EMAIL PROTECTED]> >> Message-ID: <[EMAIL PROTECTED]> >> Content-Type: text/plain; charset=US-ASCII >> >> Since I was getting nowhere trying to build FG 0.9.6 I checked it out >> from CVS instead. After getting automake 1.9.3 I was able to run >> autogen.sh and configure but it seems Makefile.in is missing in CVS. >> >> configure: creating ./config.status >> config.status: creating Makefile >> config.status: error: cannot find input file: Makefile.in >> >> That seems hard to believe though although it's true. I have no >> Makefile.in. > > > ___ > 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
[Flightgear-devel] Re: FlightGear on Mac OS X
OK, cool! So your problem (I trust) is fixed. Thank you for sticking with it and fixing your problem! Tell all your mac friends about FlightGear! 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'm sure that you are not the first to be burned with this issue. I remember having problems with another open source project (not flightgear) that required me to update make tools -- the problem usually isn't obvious -- at least to me it isn't. There's one good thing, you shouldn't have to update make tools for a few years at least. 8-) In turns out that it was using an old version of aclocal (1.6.3) and the new version of automake (1.9.3) and autoconf (1.59). So I removed the old version of aclocal so it would use v1.9.3 and now it works again. Yeah, I dropped fink when I went to Mac os x.2 (Jaguar). It sounds like a great idea for open source on mac os x, but I finally decided it was more trouble than it was worth. The above is why I don't use Fink anymore. best regards, Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
In turns out that it was using an old version of aclocal (1.6.3) and the new version of automake (1.9.3) and autoconf (1.59). So I removed the old version of aclocal so it would use v1.9.3 and now it works again. The above is why I don't use Fink anymore. On Thu, 11 Nov 2004 12:22:52 -0500, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Arthur, > > Makefile.in isn't in CVS. It is generated by automake. > > GNU Automake - http://www.gnu.org/software/automake > Freeware - Generates makefile.in files from makefile.am input files, > as part of the official GNU coding standards and build process. > Requires GNU autoconf. > On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] > wrote: > > are you running ./autogen.sh without an errors? Have you updated > aclocal and autoconf also? > > I just did a make clean and a plib build from cvs and it worked fine > under Mac os X (10.6). The rest of the build went ok also (simgear and > flightgear) though I had a modified (flightgear) Input/input.cxx and > Main/options.cxx. The FlightGear changes are for debugging some things > I was looking at at one time... > > I'm doing a 'make clean install' for SimGear and FlightGear now from > latest (1700 GMT) cvs. My plib and simgear are straight from cvs, > flightgear and data are straight from cvs (no modified local copies, > except for the FlightGear input.cxx and options.cxx files that I > mentioned above). > > Ima > > > > > Message: 8 > > Date: Thu, 11 Nov 2004 09:51:09 -0500 > > From: Arthur Wiebe <[EMAIL PROTECTED]> > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > To: FlightGear developers discussions > > <[EMAIL PROTECTED]> > > Message-ID: <[EMAIL PROTECTED]> > > > > Content-Type: text/plain; charset=US-ASCII > > > > Since I was getting nowhere trying to build FG 0.9.6 I checked it out > > from CVS instead. After getting automake 1.9.3 I was able to run > > autogen.sh and configure but it seems Makefile.in is missing in CVS. > > > > configure: creating ./config.status > > config.status: creating Makefile > > config.status: error: cannot find input file: Makefile.in > > > > That seems hard to believe though although it's true. I have no > > Makefile.in. > > > ___ > > > 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
[Flightgear-devel] Re: FlightGear on Mac OS X
Arthur, Makefile.in isn't in CVS. It is generated by automake. GNU Automake - http://www.gnu.org/software/automake Freeware - Generates makefile.in files from makefile.am input files, as part of the official GNU coding standards and build process. Requires GNU autoconf. On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] wrote: are you running ./autogen.sh without an errors? Have you updated aclocal and autoconf also? I just did a make clean and a plib build from cvs and it worked fine under Mac os X (10.6). The rest of the build went ok also (simgear and flightgear) though I had a modified (flightgear) Input/input.cxx and Main/options.cxx. The FlightGear changes are for debugging some things I was looking at at one time... I'm doing a 'make clean install' for SimGear and FlightGear now from latest (1700 GMT) cvs. My plib and simgear are straight from cvs, flightgear and data are straight from cvs (no modified local copies, except for the FlightGear input.cxx and options.cxx files that I mentioned above). Ima Message: 8 Date: Thu, 11 Nov 2004 09:51:09 -0500 From: Arthur Wiebe <[EMAIL PROTECTED]> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X To: FlightGear developers discussions <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII Since I was getting nowhere trying to build FG 0.9.6 I checked it out from CVS instead. After getting automake 1.9.3 I was able to run autogen.sh and configure but it seems Makefile.in is missing in CVS. configure: creating ./config.status config.status: creating Makefile config.status: error: cannot find input file: Makefile.in That seems hard to believe though although it's true. I have no Makefile.in. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Since I was getting nowhere trying to build FG 0.9.6 I checked it out from CVS instead. After getting automake 1.9.3 I was able to run autogen.sh and configure but it seems Makefile.in is missing in CVS. configure: creating ./config.status config.status: creating Makefile config.status: error: cannot find input file: Makefile.in That seems hard to believe though although it's true. I have no Makefile.in. On Wed, 10 Nov 2004 18:26:04 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: > I have built PLIB 1.8.3 and SimGear 0.3.7. > But building FlightGear 0.9.6 has not yet been successful. > > I used ./configure --prefix=$BUILDDIR --without-x > and then plain make. > It looked like everything was going to work until... here's a cut of > the output leading up to the error: > > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT puList.o -MD > -MP -MF ".deps/puList.Tpo" -c -o puList.o puList.cxx; \ > then mv -f ".deps/puList.Tpo" ".deps/puList.Po"; else rm -f > ".deps/puList.Tpo"; exit 1; fi > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT AirportList.o > -MD -MP -MF ".deps/AirportList.Tpo" -c -o AirportList.o > AirportList.cxx; \ > then mv -f ".deps/AirportList.Tpo" ".deps/AirportList.Po"; else rm -f > ".deps/AirportList.Tpo"; exit 1; fi > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout.o -MD > -MP -MF ".deps/layout.Tpo" -c -o layout.o layout.cxx; \ > then mv -f ".deps/layout.Tpo" ".deps/layout.Po"; else rm -f > ".deps/layout.Tpo"; exit 1; fi > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout-props.o > -MD -MP -MF ".deps/layout-props.Tpo" -c -o layout-props.o > layout-props.cxx; \ > then mv -f ".deps/layout-props.Tpo" ".deps/layout-props.Po"; else rm > -f ".deps/layout-props.Tpo"; exit 1; fi > rm -f libGUI.a > ar cru libGUI.a new_gui.o dialog.o menubar.o gui.o gui_funcs.o > gui_local.o mouse.o preset_dlg.o prop_picker.o sgVec3Slider.o > trackball.o puList.o AirportList.o layout.o layout-props.o > ranlib libGUI.a > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout-test.o > -MD -MP -MF ".deps/layout-test.Tpo" -c -o layout-test.o > layout-test.cxx; \ > then mv -f ".deps/layout-test.Tpo" ".deps/layout-test.Po"; else rm -f > ".deps/layout-test.Tpo"; exit 1; fi > g++ -I/usr/X11R6/include -D_REENTRANT -L/fgfs/lib -o layout-test > layout-test.o libGUI.a -lsgprops -lsgdebug -lsgstructure -lsgmisc > -lsgxml -lplibpw -lplibpu -lplibfnt -lplibul -framework GLUT > -framework OpenGL -framework AGL -framework Carbon -lobjc > ld: Undefined symbols: > fntTexFont::load(char const*, unsigned int, unsigned int) > make[2]: *** [layout-test] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 > > Do you have any ideas or had this error yourself? > > By the way, Mac OS X packages of PLIB are at > http://awiebe.blogdns.net/download/PLIB/MacOSX/ > > Hoping to add a flightgear and simgear package as well soon. > > > > On Wed, 10 Nov 2004 16:03:39 -0500, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Arthur > > > > I'm glad plib built for you. I only put plib and other flightgear files > > in a local tree and use --prefix so configure can find them. Also that > > way, I don't have to worry about old versions of plib that might be on > > my system somewhere. > > > > if you use --prefix with a non-system directory, you can avoid having > > to use sudo make install for library installation also. > > > > Lots of people on the list have run into problems related to old(er) > > versions of libraries on their systems in multiple paths. I'm sure > > that I ran into this one before I started using --prefix > > > > On Nov 10, 2004, at 2:49 PM, Arthur wrote: > > > > > Date: Wed, 10 Nov 2004 14:49:32 -0500 > > > From: Arthur Wiebe <[EMAIL PROTECTED]> > > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > To: FlightGear developers discussions > > > <[EMAIL PROTECTED]> > > > Message-ID: <[EMAIL PROTECTED]> > > > Content-Type: text/plain; charset=US-ASCII > > > > > >
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
I have built PLIB 1.8.3 and SimGear 0.3.7. But building FlightGear 0.9.6 has not yet been successful. I used ./configure --prefix=$BUILDDIR --without-x and then plain make. It looked like everything was going to work until... here's a cut of the output leading up to the error: if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT puList.o -MD -MP -MF ".deps/puList.Tpo" -c -o puList.o puList.cxx; \ then mv -f ".deps/puList.Tpo" ".deps/puList.Po"; else rm -f ".deps/puList.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT AirportList.o -MD -MP -MF ".deps/AirportList.Tpo" -c -o AirportList.o AirportList.cxx; \ then mv -f ".deps/AirportList.Tpo" ".deps/AirportList.Po"; else rm -f ".deps/AirportList.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout.o -MD -MP -MF ".deps/layout.Tpo" -c -o layout.o layout.cxx; \ then mv -f ".deps/layout.Tpo" ".deps/layout.Po"; else rm -f ".deps/layout.Tpo"; exit 1; fi if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout-props.o -MD -MP -MF ".deps/layout-props.Tpo" -c -o layout-props.o layout-props.cxx; \ then mv -f ".deps/layout-props.Tpo" ".deps/layout-props.Po"; else rm -f ".deps/layout-props.Tpo"; exit 1; fi rm -f libGUI.a ar cru libGUI.a new_gui.o dialog.o menubar.o gui.o gui_funcs.o gui_local.o mouse.o preset_dlg.o prop_picker.o sgVec3Slider.o trackball.o puList.o AirportList.o layout.o layout-props.o ranlib libGUI.a if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout-test.o -MD -MP -MF ".deps/layout-test.Tpo" -c -o layout-test.o layout-test.cxx; \ then mv -f ".deps/layout-test.Tpo" ".deps/layout-test.Po"; else rm -f ".deps/layout-test.Tpo"; exit 1; fi g++ -I/usr/X11R6/include -D_REENTRANT -L/fgfs/lib -o layout-test layout-test.o libGUI.a -lsgprops -lsgdebug -lsgstructure -lsgmisc -lsgxml -lplibpw -lplibpu -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Do you have any ideas or had this error yourself? By the way, Mac OS X packages of PLIB are at http://awiebe.blogdns.net/download/PLIB/MacOSX/ Hoping to add a flightgear and simgear package as well soon. On Wed, 10 Nov 2004 16:03:39 -0500, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Arthur > > I'm glad plib built for you. I only put plib and other flightgear files > in a local tree and use --prefix so configure can find them. Also that > way, I don't have to worry about old versions of plib that might be on > my system somewhere. > > if you use --prefix with a non-system directory, you can avoid having > to use sudo make install for library installation also. > > Lots of people on the list have run into problems related to old(er) > versions of libraries on their systems in multiple paths. I'm sure > that I ran into this one before I started using --prefix > > On Nov 10, 2004, at 2:49 PM, Arthur wrote: > > > Date: Wed, 10 Nov 2004 14:49:32 -0500 > > From: Arthur Wiebe <[EMAIL PROTECTED]> > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > To: FlightGear developers discussions > > <[EMAIL PROTECTED]> > > Message-ID: <[EMAIL PROTECTED]> > > Content-Type: text/plain; charset=US-ASCII > > > > > > Well... I got simgear configured. > > > > Before I didn't specify --prefix for plib or simgear. Now I made a > > directory called fgfs in / and install plib there and then specified > > that plib was installed there when configuring simgear and used the > > same prefix for simgear. Now it worked. > > This leads me to thinking it was a crazy permissions problem! > > > > Well at least it works now and I will be making a Mac OS X installer > > package for plib 1.8.3 and posting it online for other people like me. > > > > Next step is to get simgear and flightgear to compile. I guess you'll > > hear from me again soon. > > > > good luck! Use the same --prefix for plib, simgear and flightgear. Is > everything building OK now? Remember you can't mix and match release > and CVS versions, either release
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur I'm glad plib built for you. I only put plib and other flightgear files in a local tree and use --prefix so configure can find them. Also that way, I don't have to worry about old versions of plib that might be on my system somewhere. if you use --prefix with a non-system directory, you can avoid having to use sudo make install for library installation also. Lots of people on the list have run into problems related to old(er) versions of libraries on their systems in multiple paths. I'm sure that I ran into this one before I started using --prefix On Nov 10, 2004, at 2:49 PM, Arthur wrote: Date: Wed, 10 Nov 2004 14:49:32 -0500 From: Arthur Wiebe <[EMAIL PROTECTED]> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X To: FlightGear developers discussions <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII Well... I got simgear configured. Before I didn't specify --prefix for plib or simgear. Now I made a directory called fgfs in / and install plib there and then specified that plib was installed there when configuring simgear and used the same prefix for simgear. Now it worked. This leads me to thinking it was a crazy permissions problem! Well at least it works now and I will be making a Mac OS X installer package for plib 1.8.3 and posting it online for other people like me. Next step is to get simgear and flightgear to compile. I guess you'll hear from me again soon. good luck! Use the same --prefix for plib, simgear and flightgear. Is everything building OK now? Remember you can't mix and match release and CVS versions, either release plib, simgear and flightgear source OR CVS plib, simgear, flightgear source. There is also talk on the list recently about file name collisions on case preserving but not case significant file systems (like cygwin and mac os x). You'll see this when you're downloading the data from cvs under mac os x, if you're using HFS+ as opposed to a *nix file system on your Mac with a few files unless they've been fixed already. Anyway you want CVS plib to have Olivier's great joystick fixes anyway. I'm not sure they're in a release yet. I use the CVS source tree, which a few times a year gets into a non-buildable state for a day or two but is not usually a problem. I don't have Mac os X installs for anything, but one of the other Mac people (Jonathan, perhaps?) had created a Mac os X cocoa executable for FGFS. I don't recall if they had an app for installation, however. I think it was just drag and drop. I don't know if this app has been updated. I'm assuming you no longer need ./lib/libplibXXX and ./include/plib sent to you? 8-) Have fun and please let the list know how it goes. Provided you've got the dependencies installed, the Mac OS X build goes just like any other *nix clone 8-). Hopefully, you'll have no build problems once you're using --prefix. Just remember to build flightgear using ./configure --without-x unless you want to use X11 on mac os x (which is NOT installed by default). There, I think that's all the mac related screwups, I've done 8-) Enjoy the world's best Mac OS X opensource flightsim... Now if someone would just do Washington, DC scenery for flightgear. I used to have a nice DC add-on for XPlane... Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Now to building simgear on Mac OS X. I get the following output: source='matlib.cxx' object='matlib.o' libtool=no \ depfile='.deps/matlib.Po' tmpdepfile='.deps/matlib.TPo' \ depmode=gcc3 /bin/sh ../../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../../simgear -I../../.. -I/fgfs/include -g -O2 -D_REENTRANT -c -o matlib.o `test -f 'matlib.cxx' || echo './'`matlib.cxx matlib.cxx:36:19: GL/gl.h: No such file or directory make[4]: *** [matlib.o] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 ./configure goes fine. But I can't run make without the above. This is with GCC 3.3. I seem to have lost my GCC 2.95.2 installation so I have to install it before I can try with that. On Wed, 10 Nov 2004 14:49:32 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: > Well... I got simgear configured. > > Before I didn't specify --prefix for plib or simgear. Now I made a > directory called fgfs in / and install plib there and then specified > that plib was installed there when configuring simgear and used the > same prefix for simgear. Now it worked. > This leads me to thinking it was a crazy permissions problem! > > Well at least it works now and I will be making a Mac OS X installer > package for plib 1.8.3 and posting it online for other people like me. > > Next step is to get simgear and flightgear to compile. I guess you'll > hear from me again soon. > > > > > On Wed, 10 Nov 2004 14:32:39 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: > > I looked into the config.log file and it doesn't make much sense: > > > > ## --- ## > > ## confdefs.h. ## > > ## --- ## > > > > #define HAVE_INTTYPES_H 1 > > #define HAVE_LIBPTHREAD 1 > > #define HAVE_MEMORY_H 1 > > #define HAVE_STDINT_H 1 > > #define HAVE_STDLIB_H 1 > > #define HAVE_STRINGS_H 1 > > #define HAVE_STRING_H 1 > > #define HAVE_SYS_STAT_H 1 > > #define HAVE_SYS_TYPES_H 1 > > #define HAVE_UNISTD_H 1 > > #define PACKAGE "SimGear" > > #define PACKAGE_BUGREPORT "" > > #define PACKAGE_NAME "" > > #define PACKAGE_STRING "" > > #define PACKAGE_TARNAME "" > > #define PACKAGE_VERSION "" > > #define STDC_HEADERS 1 > > #define VERSION "0.3.7" > > #endif > > #ifdef __cplusplus > > extern "C" void std::exit (int) throw (); using std::exit; > > > > configure: exit 1 > > > > And using --plib-prefix=/usr/ did not work. It resulted in: > > configure: error: unrecognized option: --plib-prefix=/usr/ > > Try `./configure --help' for more information. > > > > I got PLIB 1.8.3 to compile thanks to Adam. But that didn't help > > either. I think I will try to get the release version of simgear > > instead of getting it from CVS. Don't think that will have any effect > > though. > > > > I'm also going to try to use --prefix=/onepath for plib and simgear. > > See if that works. > > > > Thanks for the replies! > > > > > > > > > > On Wed, 10 Nov 2004 19:17:06 -, Giles Robertson > > <[EMAIL PROTECTED]> wrote: > > > I've found on some pseudo-POSIX Windows systems that the build only > > > finds PLIB when you specify --plib-prefix=/usr/. Weird, but that can be > > > what it takes; and it may be similar on OS X. > > > > > > The other tactic is to specify --prefix=/fg or some other value for > > > every compile; PLIB, SimGear, FGFS. > > > > > > My 2 cents. > > > > > > Giles Robertson > > > > > > > > > > > > -Original Message- > > > From: Curtis L. Olson [mailto:[EMAIL PROTECTED] > > > Sent: 10 November 2004 18:59 > > > To: FlightGear developers discussions > > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > > > Arthur Wiebe wrote: > > > > > > >Hello. I think I have plib built and installed. Using GCC 3.3 and PLIB > > > >straight from CVS 2004-11-08. > > > > > > > >Looking in /usr/include/plib and /usr/lib/ it looks like plib is > > > installed. > > > > > > > >The only problem I now have is when trying to configure simgear from > > > >CVS (same date) I get: > > > > > > > >checking plib/ul.h usability... no > > > >checking plib/ul.h presence... yes > > > >configure: WARN
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Well... I got simgear configured. Before I didn't specify --prefix for plib or simgear. Now I made a directory called fgfs in / and install plib there and then specified that plib was installed there when configuring simgear and used the same prefix for simgear. Now it worked. This leads me to thinking it was a crazy permissions problem! Well at least it works now and I will be making a Mac OS X installer package for plib 1.8.3 and posting it online for other people like me. Next step is to get simgear and flightgear to compile. I guess you'll hear from me again soon. On Wed, 10 Nov 2004 14:32:39 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: > I looked into the config.log file and it doesn't make much sense: > > ## --- ## > ## confdefs.h. ## > ## --- ## > > #define HAVE_INTTYPES_H 1 > #define HAVE_LIBPTHREAD 1 > #define HAVE_MEMORY_H 1 > #define HAVE_STDINT_H 1 > #define HAVE_STDLIB_H 1 > #define HAVE_STRINGS_H 1 > #define HAVE_STRING_H 1 > #define HAVE_SYS_STAT_H 1 > #define HAVE_SYS_TYPES_H 1 > #define HAVE_UNISTD_H 1 > #define PACKAGE "SimGear" > #define PACKAGE_BUGREPORT "" > #define PACKAGE_NAME "" > #define PACKAGE_STRING "" > #define PACKAGE_TARNAME "" > #define PACKAGE_VERSION "" > #define STDC_HEADERS 1 > #define VERSION "0.3.7" > #endif > #ifdef __cplusplus > extern "C" void std::exit (int) throw (); using std::exit; > > configure: exit 1 > > And using --plib-prefix=/usr/ did not work. It resulted in: > configure: error: unrecognized option: --plib-prefix=/usr/ > Try `./configure --help' for more information. > > I got PLIB 1.8.3 to compile thanks to Adam. But that didn't help > either. I think I will try to get the release version of simgear > instead of getting it from CVS. Don't think that will have any effect > though. > > I'm also going to try to use --prefix=/onepath for plib and simgear. > See if that works. > > Thanks for the replies! > > > > > On Wed, 10 Nov 2004 19:17:06 -, Giles Robertson > <[EMAIL PROTECTED]> wrote: > > I've found on some pseudo-POSIX Windows systems that the build only > > finds PLIB when you specify --plib-prefix=/usr/. Weird, but that can be > > what it takes; and it may be similar on OS X. > > > > The other tactic is to specify --prefix=/fg or some other value for > > every compile; PLIB, SimGear, FGFS. > > > > My 2 cents. > > > > Giles Robertson > > > > > > > > -Original Message- > > From: Curtis L. Olson [mailto:[EMAIL PROTECTED] > > Sent: 10 November 2004 18:59 > > To: FlightGear developers discussions > > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > > > Arthur Wiebe wrote: > > > > >Hello. I think I have plib built and installed. Using GCC 3.3 and PLIB > > >straight from CVS 2004-11-08. > > > > > >Looking in /usr/include/plib and /usr/lib/ it looks like plib is > > installed. > > > > > >The only problem I now have is when trying to configure simgear from > > >CVS (same date) I get: > > > > > >checking plib/ul.h usability... no > > >checking plib/ul.h presence... yes > > >configure: WARNING: plib/ul.h: present but cannot be compiled > > >configure: WARNING: plib/ul.h: check for missing prerequisite > > headers? > > >configure: WARNING: plib/ul.h: see the Autoconf documentation > > >configure: WARNING: plib/ul.h: section "Present But Cannot Be > > Compiled" > > >configure: WARNING: plib/ul.h: proceeding with the preprocessor's > > result > > >configure: WARNING: plib/ul.h: in the future, the compiler will take > > precedence > > >configure: WARNING: ## -- > > ## > > >configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. > > ## > > >configure: WARNING: ## -- > > ## > > >checking for plib/ul.h... yes > > >checking for plib 1.6.0 or newer... wrong version > > >configure: error: Install plib 1.6.0 or later first... > > > > > >That has to mean something. > > > > > >I tried changing the version in ul.h but that didn't help :). Could > > >you send me your compiled files (from /usr/lib/libplibXXX and > > >/usr/include/plib) and see if if that works? I would love to make an > > >installer package for Mac OS X which would install plib for other OSX > > >users without hav
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
I looked into the config.log file and it doesn't make much sense: ## --- ## ## confdefs.h. ## ## --- ## #define HAVE_INTTYPES_H 1 #define HAVE_LIBPTHREAD 1 #define HAVE_MEMORY_H 1 #define HAVE_STDINT_H 1 #define HAVE_STDLIB_H 1 #define HAVE_STRINGS_H 1 #define HAVE_STRING_H 1 #define HAVE_SYS_STAT_H 1 #define HAVE_SYS_TYPES_H 1 #define HAVE_UNISTD_H 1 #define PACKAGE "SimGear" #define PACKAGE_BUGREPORT "" #define PACKAGE_NAME "" #define PACKAGE_STRING "" #define PACKAGE_TARNAME "" #define PACKAGE_VERSION "" #define STDC_HEADERS 1 #define VERSION "0.3.7" #endif #ifdef __cplusplus extern "C" void std::exit (int) throw (); using std::exit; configure: exit 1 And using --plib-prefix=/usr/ did not work. It resulted in: configure: error: unrecognized option: --plib-prefix=/usr/ Try `./configure --help' for more information. I got PLIB 1.8.3 to compile thanks to Adam. But that didn't help either. I think I will try to get the release version of simgear instead of getting it from CVS. Don't think that will have any effect though. I'm also going to try to use --prefix=/onepath for plib and simgear. See if that works. Thanks for the replies! On Wed, 10 Nov 2004 19:17:06 -, Giles Robertson <[EMAIL PROTECTED]> wrote: > I've found on some pseudo-POSIX Windows systems that the build only > finds PLIB when you specify --plib-prefix=/usr/. Weird, but that can be > what it takes; and it may be similar on OS X. > > The other tactic is to specify --prefix=/fg or some other value for > every compile; PLIB, SimGear, FGFS. > > My 2 cents. > > Giles Robertson > > > > -Original Message----- > From: Curtis L. Olson [mailto:[EMAIL PROTECTED] > Sent: 10 November 2004 18:59 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > Arthur Wiebe wrote: > > >Hello. I think I have plib built and installed. Using GCC 3.3 and PLIB > >straight from CVS 2004-11-08. > > > >Looking in /usr/include/plib and /usr/lib/ it looks like plib is > installed. > > > >The only problem I now have is when trying to configure simgear from > >CVS (same date) I get: > > > >checking plib/ul.h usability... no > >checking plib/ul.h presence... yes > >configure: WARNING: plib/ul.h: present but cannot be compiled > >configure: WARNING: plib/ul.h: check for missing prerequisite > headers? > >configure: WARNING: plib/ul.h: see the Autoconf documentation > >configure: WARNING: plib/ul.h: section "Present But Cannot Be > Compiled" > >configure: WARNING: plib/ul.h: proceeding with the preprocessor's > result > >configure: WARNING: plib/ul.h: in the future, the compiler will take > precedence > >configure: WARNING: ## -- > ## > >configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. > ## > >configure: WARNING: ## -- > ## > >checking for plib/ul.h... yes > >checking for plib 1.6.0 or newer... wrong version > >configure: error: Install plib 1.6.0 or later first... > > > >That has to mean something. > > > >I tried changing the version in ul.h but that didn't help :). Could > >you send me your compiled files (from /usr/lib/libplibXXX and > >/usr/include/plib) and see if if that works? I would love to make an > >installer package for Mac OS X which would install plib for other OSX > >users without having to compile it. > > > > > > The details of the configure script failure can be found in the > config.log file. That may shed some light on exactly what is going > wrong. > > Curt. > > -- > Curtis Olsonhttp://www.flightgear.org/~curt > HumanFIRST Program http://www.humanfirst.umn.edu/ > FlightGear Project http://www.flightgear.org > Unique text:2f585eeea02e2c79d7b1d8c4963bae2d > > ___ > 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 > -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: FlightGear on Mac OS X
I've found on some pseudo-POSIX Windows systems that the build only finds PLIB when you specify --plib-prefix=/usr/. Weird, but that can be what it takes; and it may be similar on OS X. The other tactic is to specify --prefix=/fg or some other value for every compile; PLIB, SimGear, FGFS. My 2 cents. Giles Robertson -Original Message- From: Curtis L. Olson [mailto:[EMAIL PROTECTED] Sent: 10 November 2004 18:59 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X Arthur Wiebe wrote: >Hello. I think I have plib built and installed. Using GCC 3.3 and PLIB >straight from CVS 2004-11-08. > >Looking in /usr/include/plib and /usr/lib/ it looks like plib is installed. > >The only problem I now have is when trying to configure simgear from >CVS (same date) I get: > >checking plib/ul.h usability... no >checking plib/ul.h presence... yes >configure: WARNING: plib/ul.h: present but cannot be compiled >configure: WARNING: plib/ul.h: check for missing prerequisite headers? >configure: WARNING: plib/ul.h: see the Autoconf documentation >configure: WARNING: plib/ul.h: section "Present But Cannot Be Compiled" >configure: WARNING: plib/ul.h: proceeding with the preprocessor's result >configure: WARNING: plib/ul.h: in the future, the compiler will take precedence >configure: WARNING: ## -- ## >configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## >configure: WARNING: ## -- ## >checking for plib/ul.h... yes >checking for plib 1.6.0 or newer... wrong version >configure: error: Install plib 1.6.0 or later first... > >That has to mean something. > >I tried changing the version in ul.h but that didn't help :). Could >you send me your compiled files (from /usr/lib/libplibXXX and >/usr/include/plib) and see if if that works? I would love to make an >installer package for Mac OS X which would install plib for other OSX >users without having to compile it. > > The details of the configure script failure can be found in the config.log file. That may shed some light on exactly what is going wrong. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ 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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur Wiebe wrote: Hello. I think I have plib built and installed. Using GCC 3.3 and PLIB straight from CVS 2004-11-08. Looking in /usr/include/plib and /usr/lib/ it looks like plib is installed. The only problem I now have is when trying to configure simgear from CVS (same date) I get: checking plib/ul.h usability... no checking plib/ul.h presence... yes configure: WARNING: plib/ul.h: present but cannot be compiled configure: WARNING: plib/ul.h: check for missing prerequisite headers? configure: WARNING: plib/ul.h: see the Autoconf documentation configure: WARNING: plib/ul.h: section "Present But Cannot Be Compiled" configure: WARNING: plib/ul.h: proceeding with the preprocessor's result configure: WARNING: plib/ul.h: in the future, the compiler will take precedence configure: WARNING: ## -- ## configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## configure: WARNING: ## -- ## checking for plib/ul.h... yes checking for plib 1.6.0 or newer... wrong version configure: error: Install plib 1.6.0 or later first... That has to mean something. I tried changing the version in ul.h but that didn't help :). Could you send me your compiled files (from /usr/lib/libplibXXX and /usr/include/plib) and see if if that works? I would love to make an installer package for Mac OS X which would install plib for other OSX users without having to compile it. The details of the configure script failure can be found in the config.log file. That may shed some light on exactly what is going wrong. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear on Mac OS X
Hello. I think I have plib built and installed. Using GCC 3.3 and PLIB straight from CVS 2004-11-08. Looking in /usr/include/plib and /usr/lib/ it looks like plib is installed. The only problem I now have is when trying to configure simgear from CVS (same date) I get: checking plib/ul.h usability... no checking plib/ul.h presence... yes configure: WARNING: plib/ul.h: present but cannot be compiled configure: WARNING: plib/ul.h: check for missing prerequisite headers? configure: WARNING: plib/ul.h: see the Autoconf documentation configure: WARNING: plib/ul.h: section "Present But Cannot Be Compiled" configure: WARNING: plib/ul.h: proceeding with the preprocessor's result configure: WARNING: plib/ul.h: in the future, the compiler will take precedence configure: WARNING: ## -- ## configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## configure: WARNING: ## -- ## checking for plib/ul.h... yes checking for plib 1.6.0 or newer... wrong version configure: error: Install plib 1.6.0 or later first... That has to mean something. I tried changing the version in ul.h but that didn't help :). Could you send me your compiled files (from /usr/lib/libplibXXX and /usr/include/plib) and see if if that works? I would love to make an installer package for Mac OS X which would install plib for other OSX users without having to compile it. On Wed, 10 Nov 2004 10:07:51 -0800, Adam Dershowitz <[EMAIL PROTECTED]> wrote: > OK, > I now have gotten plib to compile. No promises on the functionality. It > seems that jsMacOSX.cxx contained a LPVOID cast. I can't figure out what > this is. It seems to be a Windows thing. I removed that. I hate to remove > a cast without understanding it, but it does now compile. > So, again, here are the diffs of the two files that I changed from the > original to my own version. > > > > diff jsMacOSX.cxx jsMacOSX_org.cxx > > 17,19c17 > < //int jsJoystick::kNumDevices = 32 ; > < int jsJoystick::kNumDevices = JS_MAX_OSX_DEVICES ; > < > --- > > int jsJoystick::kNumDevices = 32 ; > 21,22c19 > < //io_object_t jsJoystick::ioDevices[kNumDevices]; > < io_object_t jsJoystick::ioDevices[JS_MAX_OSX_DEVICES] ; > --- > > io_object_t jsJoystick::ioDevices[kNumDevices]; > 132,133c129,130 > < HRESULT pluginResult = (*plugin)->QueryInterface(plugin, > < CFUUIDGetUUIDBytes(kIOHIDDeviceInterfaceID), &hidDev); > --- > > HRESULT pluginResult = (*plugin)->QueryInterface(plugin, > > CFUUIDGetUUIDBytes(kIOHIDDeviceInterfaceID), &(LPVOID) > > hidDev); > > > > > diff js.h js_org.h > 35,36d34 > < #define JS_MAX_OSX_DEVICES 32 > < > 97c95 > < static int kNumDevices; > --- > > static const int kNumDevices; > 99,100c97 > < // static io_object_t ioDevices[kNumDevices]; > < static io_object_t jsJoystick::ioDevices[JS_MAX_OSX_DEVICES] ; > --- > > static io_object_t ioDevices[kNumDevices]; > > > So my build steps were 1)just to download with CVS. > 2) make the above edits. > 3) ./autogen.sh > 4)./configure --prefix=$BUILDDIR (or whatever) > 5) make install. > > Good luck, and let me know if it works for you. > > > > -- Adam > > > From: Arthur Wiebe <[EMAIL PROTECTED]> > > Reply-To: Arthur Wiebe <[EMAIL PROTECTED]> > > Date: Wed, 10 Nov 2004 08:45:01 -0500 > > To: <[EMAIL PROTECTED]> > > Subject: FlightGear on Mac OS X > > > > Hello, > > I just have a question. What did you do to get plib to compile? I > > tried some things but couldn't get it to work so I just got it from > > CVS which did work but simgear doesn't recognize it. > > And what version of plib did you build? > > > > Thanks. > > -- > > > > -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
