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 ap
[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 co
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
>
>
> >
>
ar 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
>
ar-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 gu
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 s
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 pret
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 becau
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
> 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 .f
.
> 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
> Applicatio
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
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
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 pr
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/
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 / -pri
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, /
oups: 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
>> es
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 lib
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.
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_REENTRAN
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 an
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
TECTED]>
> 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
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
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
[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
> 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:
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 simpl
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
> 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 o
VS 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: F
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/soft
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
> 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
> &g
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
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
>
ith 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
004, 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:
ows 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
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.
> >
> > Gile
> 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
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 i
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 p
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 usabilit
45 matches
Mail list logo
