Re: [Flightgear-devel] Aircraft Download/Install App

[Arthur Wiebe]

> Why do you think that? I've not seen any negative responses.
> It's like everything else, a good idea is always welcome but like you,
> others might not have time to develop it (right away).
>
> Erik
>

Well it may be a good idea, but just not worth the development time
for most people. But if anyone ever wants to go at it, let me know.
I'd be able to help a little, but just not enough to do everything.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Aircraft Download/Install App

[Arthur Wiebe]

> And maybe it would also be a good idea to package aircraft and scenery
> in rpm or deb format. That way you don't have to worry about
> dependencies like how so many planes use the p51 instruments. fgadmin
> could run it's own rpm or deb database. Not sure how this would work on
> non-unix platforms, but I don't see any showstoppers.
>
> Josh
>

At first I thought you were joking. But I guess it would work.

> ... and we could call it ... *pause* ... fgadmin!

I tried fgadmin (just now actually) and couldn't figure out how to use
it right away. Clicking "Select All" or "Deselect All" did nothing.
Didn't even get a notice.
The GUI is really bad I have to say.

But as it seems to be a bad idea, I guess we can forget this thread.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] Aircraft Download/Install App

[Arthur Wiebe]

This is an idea that's been floating around in my head for awhile,
mainly because there is currently no *very easy* way for a newbie to
install new aircraft in FlightGear. Unless that user is used to going
through Program\ Files in Windows and through package contents on OSX.

The idea is for an aircraft application. This application would
download (preferrably an XML file) from a server, parse, and through a
GUI have the ability to select aircraft, see details including
previews, press a button to download and install.
The application would guess the most likely places for where to
install. But let the user change it of course.

The application would be written in C++ using the wxWidgets framework
so that it will look and work right on all platforms.

But there's no way I'm going to take it on myself. /me sick of that.
So any takers? Or is it a rotten idea I should never have posted
about? Or perhaps even something already discussed.

--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Request to the Mac folk

[Arthur Wiebe]

> As I said, producing a panther build should be doable by someone with 
> Panther, or if you get many complaints, I can set up a cross-build 
> environment to target Panther myself; I'm just being lazy on the assumption 
> flight sim users are probably early-ish adopters and already have Tiger...
>
>
> H&HJames
>

I had made that assumption too when doing the FlightGear 0.9.9 release
build for Mac. I figured if someone wanted a Panther build they would
make a build and make it available.
Cross-building is doable but it takes a bit of work. And I believe you
would have to modifiy the FlightGear source as well (but not sure).

Anyway soon after I released 0.9.9 posts started popping up in the
forums about it not working. :)
But what else can you expect when it's been downloaded 8817 times.

I might make use of the Sourceforge.net compile farm to make on a more
compatible target.

--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] FlightGear 0.9.9 for Mac OS X Available

[Arthur Wiebe]

From: http://macflightgear.sourceforge.net/

It's not a complete universal binary because of some unexpected
problems. There's a few features I didn't have time to get in like a
GUI helper for aircraft/scenery installation and atlas integration.
But here it is.

--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] RenderTexture::BeginCapture(): Texture isnotinitialized!

[Arthur Wiebe]

> I'll experiment as well - I had some strange issues earlier in the year
> building FG with my own X-Code projects; I was being more ambitious, and
> building PLIB and SimGear as frameworks, but on reflection that's not such a
> great idea. One change I have made is to use a 'copy files' stage for your
> Prepare files; otherwise they always touch config.h / version.h, and that
> tirggers a dependant rebuild of many files for me. The Copy Files stage has
> the right 'only re-copy if src mod time is more recent than existing
> destination' logic.
>
> H&HJames
>

I have fixed one problem. After making some changes to the SimGear
project fgfs launches well. So it fixed the problem in this thread.
The project file changes have been committed to cvs.

But the spash image problem is still there. So something is still not
being done right. Hopefully I can figure this one out soon!

And good idea with the copy files thing. I never thought about that.
And will change that in cvs as well as soon as this other problem is
fixed.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] RenderTexture::BeginCapture(): Texture isnotinitialized!

[Arthur Wiebe]

> >I have found the problem. My Xcode projects seem to be buggy. The PLIB
> >project is fine but something is wrong with the SimGear project.
> >
> >I just built using the autoconf system and everything worked fine. It
> >even fixed my spash screen problem! :)
> >I'll try to have it fixed by tomorrow afternoon if possible.
> >
> >
>
> Woohoo!
>
> Curt.
>

Yeah, wooho.
But the only problem is I *have* to use Xcode projects in order to
build universal binaries as autoconf can't handle it very well.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] RenderTexture::BeginCapture(): Texture isnotinitialized!

[Arthur Wiebe]

I have found the problem. My Xcode projects seem to be buggy. The PLIB
project is fine but something is wrong with the SimGear project.

I just built using the autoconf system and everything worked fine. It
even fixed my spash screen problem! :)
I'll try to have it fixed by tomorrow afternoon if possible.

On 11/18/05, Vivian Meazza <[EMAIL PROTECTED]> wrote:
> Arthur Wiebe
>
> >
> > On 11/18/05, Vivian Meazza <[EMAIL PROTECTED]> wrote:
> > > Arthur Wiebe
> > >
> > > > Subject: [Flightgear-devel] RenderTexture::BeginCapture(): Texture is
> > > > notinitialized!
> > > >
> > > > When running fgfs 0.9.9 I get this output:
> > > >
> > > > opening file:
> > > > /Users/arthur/Projects/FlightGearOSX/data//Navaids/carrier_nav.dat
> > > > /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
> > > > RenderTexture::BeginCapture(): Texture is not initialized!
> > > >
> > /Users/arthur/Projects/FlightGear/../SimGear/SimGear/simgear/threads/SGThr
> > > > ead.hxx:233:
> > > > failed assertion `status == 0'
> > > > Abort trap
> > > >
> > > > At first if failed right after this line:
> > > > /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
> > > >
> > > > But then I uncompressed TACAN_freq.dat.gz and carrier_nav.dat.gz and
> > > > got past that. And now it aborts with RenderTexture.
> > > >
> > > > As long as things go like this there'll be no Mac release anytime
> > soon.
> > >
> > > There should be no need to uncompress either file.
> > >
> > > Vivian
> > >
> > >
> >
> > There isn't. It was one of those things that comes from the top of
> > your head but ends up being smoke.
>
> Good, otherwise I would have to panic :-)
>
> V.
>
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] RenderTexture::BeginCapture(): Texture is not initialized!

[Arthur Wiebe]

I have the feeling this is actually a problem with the xcode project
files. I'm going to build using makefiles and see what happens. It
could be that something isn't be compiled correctly.

On 11/18/05, Ima Sudonim <[EMAIL PROTECTED]> wrote:
> >
> James,
>
> Sorry to hear you're having so much trouble. Unfortunately,
> everything is working for me just fine with latest CVS...
>
> > opening file: /Users/arthur/Projects/FlightGearOSX/data//Navaids/
> > carrier_nav.dat
> > /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
> > RenderTexture::BeginCapture(): Texture is not initialized!
> >
>
> I've seen the RenderTexture::BeginCapture() message for a while but
> it doesn't stop fg from loading.  Help is still broken, but we knew
> that 8-(  I get sound but the sound dialog mute checkbox has no
> effect, but we knew that too 8-(
>
> > /Users/arthur/Projects/FlightGear/../SimGear/SimGear/simgear/
> > threads/SGThread.hxx:233:
> > failed assertion `status == 0'
> >
>
> I take it you're building FlightGear --with-threads, I am too. also --
> without-x
>
> My log after starting, running help, turning sound off and on and
> exiting is:
>
> Using Mac OS X hack for initializing C++ stdio...
> help app is open
> opening file: /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/
> carrier_nav.dat
> /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/TACAN_freq.dat
> Failed to find runway 28R at airport KDCA
> RenderTexture::BeginCapture(): Texture is not initialized!
> Initialising callsign using 'Aircraft/c172p/Models/c172p.xml'
> Initializing Nasal Electrical System
> WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/
> w080n30/w077n38/1l'
> sh: line 1: netscape: command not found
>
> FlightGear also works with --aircraft=A-10cl
>
> Using Mac OS X hack for initializing C++ stdio...
> help app is open
> opening file: /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/
> carrier_nav.dat
> /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/TACAN_freq.dat
> Failed to find runway 28R at airport KDCA
> RenderTexture::BeginCapture(): Texture is not initialized!
> Reading xml electrical system model from /Users/ima/Desktop/
> FlightGear/fgdev9.9/data/Aircraft/A-10/Systems/A-10-electrical.xml
> Initialising callsign using 'Aircraft/A-10/Models/A-10-model.xml'
> WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/
> w080n30/w077n38/1l'
>
> > Abort trap
> >
> > At first if failed right after this line:
> > /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
> >
> > But then I uncompressed TACAN_freq.dat.gz and carrier_nav.dat.gz and
> > got past that. And now it aborts with RenderTexture.
> >
> > As long as things go like this there'll be no Mac release anytime
> > soon.
> >
> >
>
> Try a make clean in simgear and flightgear and rebuild. What version
> of mac os x and gcc/xcode are you using? I am on: 10.4.3, gcc --
> version 4.0.1 (build 5247), xcode 2.2 (which I'm not using, I only
> build from the command line). I am using latest cvs for plib,
> simgear, and flightgear
>
> As strange as it sounds, you might try rebooting. I know, I have to
> do it at least 4 times a year, too! 8-) VERY frustrating  Not
> at all like a certain other os I could mention.
>
> Sorry I haven't been feeling very well the last few days and haven't
> been paying close attention... the weather is a balmy yet humid below
> freezing Uggh! Just the thing for arthritis... 8-(
>
> Good luck!
>
> Thanks everyone for your work on this release which I hope to find
> time (and energy) to play with soon.
>
> Ima
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] 0.9.9 Bug

[Arthur Wiebe]

> Yes, that is correct.  But, if I enable sound, the bug still shows
> up.  In other words, if I start with --enable-sound then it starts
> with sound, as it should, but the dialog box does not allow me to
> turn it off.
>
>
> --Adam
>

I noticed that too but never thought anything of it. So I can confirm it.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] RenderTexture::BeginCapture(): Texture is notinitialized!

[Arthur Wiebe]

On 11/18/05, Vivian Meazza <[EMAIL PROTECTED]> wrote:
> Arthur Wiebe
>
> > Subject: [Flightgear-devel] RenderTexture::BeginCapture(): Texture is
> > notinitialized!
> >
> > When running fgfs 0.9.9 I get this output:
> >
> > opening file:
> > /Users/arthur/Projects/FlightGearOSX/data//Navaids/carrier_nav.dat
> > /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
> > RenderTexture::BeginCapture(): Texture is not initialized!
> > /Users/arthur/Projects/FlightGear/../SimGear/SimGear/simgear/threads/SGThr
> > ead.hxx:233:
> > failed assertion `status == 0'
> > Abort trap
> >
> > At first if failed right after this line:
> > /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
> >
> > But then I uncompressed TACAN_freq.dat.gz and carrier_nav.dat.gz and
> > got past that. And now it aborts with RenderTexture.
> >
> > As long as things go like this there'll be no Mac release anytime soon.
>
> There should be no need to uncompress either file.
>
> Vivian
>
>

There isn't. It was one of those things that comes from the top of
your head but ends up being smoke.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] RenderTexture::BeginCapture(): Texture is not initialized!

[Arthur Wiebe]

When running fgfs 0.9.9 I get this output:

opening file: /Users/arthur/Projects/FlightGearOSX/data//Navaids/carrier_nav.dat
/Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat
RenderTexture::BeginCapture(): Texture is not initialized!
/Users/arthur/Projects/FlightGear/../SimGear/SimGear/simgear/threads/SGThread.hxx:233:
failed assertion `status == 0'
Abort trap

At first if failed right after this line:
/Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat

But then I uncompressed TACAN_freq.dat.gz and carrier_nav.dat.gz and
got past that. And now it aborts with RenderTexture.

As long as things go like this there'll be no Mac release anytime soon.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Release of v0.9.9 source code

[Arthur Wiebe]

Finally! :)

Is there an official major changes list? Something to tell users what
has really changed since 0.9.8?

On 11/18/05, Erik Hofman <[EMAIL PROTECTED]> wrote:
> Curtis L. Olson wrote:
> > Hello everyone,
> >
> > FlightGear v0.9.9 is now final.  The source code is propagating through
> > to the mirrors.  If you have built an 'official' binary version of
> > FlightGear in the past, it would be great if you could build a binary
> > for v0.9.9 as well.  I'm going to make an 'official' v0.9.9 announcment
> > in a day or two and I'd like to have precompiled binaries available for
> > as many platforms as possible.
>
> I must admit that, after looking at the version history list, and all
> the updates between 0.9.8 and 0.9.9, I can't help but feeling proud to
> be part of this community. It amazes me how much progress there is
> between all the individual releases, and this one in particular.
>
> Agreed, there are still areas othat could need improvement (and I
> already have my TODO box filling up again), but this really is a releas
> that could have been called 1.0
>
> After this release we'll only accept bug-fixes to the code, except for
> the new JSBSim version. Any major code changes that are not intended to
> fix one or more bugs will have to wait. This has two major benefits, it
>   will give anybody some time to sit back an enjoy using FlightGear
> during the holidays and we'll have a rock solid FlightGear version 1.0
> ready somewhere early next year.
>
> Congratulations with this release everybody!
>
> Erik
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] XCode project files

[Arthur Wiebe]

You need to make os_specific_s::elementEnumerator not static as you
did but that's the only change I needed to make using the latest plib
cvs.
I'll add more detail in the ReadMe.

I believe there are some more changes you need to make in the official
plib 1.8.4 release but I don't remember them.
You can try searching the plib mailing list archives as that's where I
found the fix.

On 11/16/05, Adam Dershowitz <[EMAIL PROTECTED]> wrote:
>
>
> --Adam
>
>
>
> On Nov 14, 2005, at 7:23 AM, Arthur Wiebe wrote:
>
> >> Please do commit them, I've had hand-rolled projects for all three
> >> for some
> >> time, but they're out of sync. If I find any issues, I'll let you
> >> know.
> >>
> >> James
> >>
> >
> > OK, they are available now. I quickly wrote ReadMe's for them.
> >
> > https://sourceforge.net/cvs/?group_id=126825
> >
> > To checkout:
> > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/
> > macflightgear
> > co -P flightgear
> > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/
> > macflightgear
> > co -P SimGear
> > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/
> > macflightgear
> > co -P PLIB
> >
> > I will also commit the new macstart source soon.
> > ___
> > Flightgear-devel mailing list
> > Flightgear-devel@flightgear.org
> > http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> > 2f585eeea02e2c79d7b1d8c4963bae2d
>
> Arthur,
>
> I am building plib right now, and I got an error:
> g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" -
> DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -
> DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -
> DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -
> DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  -I. -I. -I../../src/util-g -
> O2 -Wall -c -o jsMacOSX.o `test -f 'jsMacOSX.cxx' || echo
> './'`jsMacOSX.cxx
> jsMacOSX.cxx:278: error: cannot declare member function 'static void
> os_specific_s::elementEnumerator(const void*, void*)' to have static
> linkage
> make[2]: *** [jsMacOSX.o] Error 1
> make[1]: *** [install-recursive] Error 1
> make: *** [install-recursive] Error 1
>
>
> In your ReadMe on plib is says:
> NOTE: PLIB 1.8.4 does not build without making some changes in the
> code. In the CVS version as of 2005-11-04 a small change in
> jsMacOSX.cxx is needed.
>
> Can you give me more of a clue about the details of the change?  Can
> we get the change into plib?
>
> What I tried was just removing "static"  from line 278 and so far it
> got past that section, and is still compiling.
>
> I ended up building from the command line and I also hit a snag with
> pwMacOSX.cxx needed some compiler flags that were not set.
>
>
> --Adam
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] XCode project files

[Arthur Wiebe]

 > Please do commit them, I've had hand-rolled projects for all three for some
> time, but they're out of sync. If I find any issues, I'll let you know.
>
> James
>

OK, they are available now. I quickly wrote ReadMe's for them.

https://sourceforge.net/cvs/?group_id=126825

To checkout:
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/macflightgear
co -P flightgear
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/macflightgear
co -P SimGear
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/macflightgear
co -P PLIB

I will also commit the new macstart source soon.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] XCode project files

[Arthur Wiebe]

On 11/14/05, Ima Sudonim <[EMAIL PROTECTED]> wrote:
> > Please do commit them, I've had hand-rolled projects for all three
> > for some time, but they're out of sync. If I find any issues, I'll
> > let you know.
>
> Is it worth creating a developer directory under FlightGear CVS to
> contain things like these xcode project files and developer
> instructions for cygwin here  flightgear-users@flightgear.org/2485584.html> mentioned on the
> flightgear-user list or Norm's cygwin openal work (or at least a link
> to the current versions)?
>
> Maybe developer could have os-specific directories like macosx,
> cygwin, etc or just put everything in developer directory.
>
> These aren't utils and probably don't belong in the utils
> directory... but this would keep them in a standard place accessible
> to everyone from the source tree. It seems like we see similar
> problems that people are maintaining by themselves (projects (build
> files) for xcode and for MS visual C/C++ come to mind)
>
> thanks!
>
> Ima
>
>
>

This would require someone to maintain the project files. I plan on
leaving the FlightGear project soon after the 0.9.9 release so
wouldn't be able to. It just drains too much time. It was a good
experience though with making the mac version more user friendly.

I'll still commit the Xcode projects to macflightgear CVS later today
and then we'll see what happens.
https://sourceforge.net/cvs/?group_id=126825
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,

[Arthur Wiebe]

Yeah, oops what's wrong with topposting? ;)

On 11/12/05, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> * Curtis L. Olson -- Saturday 12 November 2005 21:03:
> > Hey, what's wrong with "ed /var/mail/curt" ...
>
> Hey, and what's wrong with "mimencode -u" and "recode utf8:latin1"?
>
> As I said: it would be nicer in ASCII, but base64 isn't an offense,
> unlike HTML, fullquoting, topposting, which are the real annoyances
> on the net.  :-P
>

The fact is most people do whatever is default for their mailer. For
me it's encoding and replies are top posted. These settings make sense
for most people although some choose to live in the stone age.

For GMail users not replying at the top and just cutting into the body
like this is a real annoyance :)

> m.
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,

[Arthur Wiebe]

On 11/12/05, Martin Spott <[EMAIL PROTECTED]> wrote:
> Hello Melchior,
>
> Melchior FRANZ wrote:
>
> > This is very standard base64 encoding. Every semi-decent mailer should
> > be able to display this. Of course, it would be better in readable
> > ASCII, but I wouldn't say it's crap. Your mailer *is* crap!  :-P
>
> You know as good as I do that by common practice encoded emails don't
> belong into mailing lists - unless explicitly stated. Today we have
> base64 encoded mails, maybe tomorrow sombody thinks he'd post uuencoded
> mails he and tells us that every semi-decent mailer should be able to
> display this - which is to the same grade correct as your statement is.
>
> But all this doesn't change the fact that encoded emails in a mailing
> list are a nuisance. I wrote Arthur privately before and he simply
> didn't respond at all. Every semi-decent list member should do this,

Martin, like I said in the other thread, I never received a private
email from you. Unless it's in the spam folder.

>
> Martin.
> --
>  Unix _IS_ user friendly - it's just selective about who its friends are !
> --
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,

[Arthur Wiebe]

On 11/12/05, Curtis L. Olson <[EMAIL PROTECTED]> wrote:
> Melchior FRANZ wrote:
>
> >* Martin Spott -- Saturday 12 November 2005 20:43:
> >
> >
> >>>Z2h0Z2Vhci1kZXZlbAo+IDJmNTg1ZWVlYTAyZTJjNzlkN2IxZDhjNDk2M2JhZTJkCj4KCgoKLS0K
> >>>PEFydGh1ci8+Ci0gaHR0cDovL3NvdXJjZWZvcmdlLm5ldC91c2Vycy9hcnRvb3JvLwotIGh0dHA6
> >>>Ly9hcnRvb3JvLmJsb2dzcG90LmNvbQo=
> >>>
> >>>
> >>So, why are you posting this crap ? Please stop it,
> >>
> >>
> >
> >This is very standard base64 encoding. Every semi-decent mailer should
> >be able to display this. Of course, it would be better in readable
> >ASCII, but I wouldn't say it's crap. Your mailer *is* crap!  :-P
> >
> >
>
> Hey, what's wrong with "ed /var/mail/curt" ...
>
> 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
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


Hey Martin. Complain to Gmail maybe. I actually just figured out now
how to send ASCII. >> Plain Text.
Before all it did was remove formatting.

So if it makes you happier I'll do so from now on.
--

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] diff for browser change for mac os x to use

[Arthur Wiebe]

Sorry Martin. I never received an email from you. It may have gone into spam.But sure. No encoded email from me anymore.On 11/12/05, Martin Spott <
[EMAIL PROTECTED]> wrote:Arthur Wiebe wrote:
[...]> SSBhZ3JlZSB3aXRoIEphbWVzLiBJJ3ZlIGJlZW4gdXNpbmcgdGhlIC0tb3Blbi13aXRoIG9wdGlvAs Arthur obviously decided to ignore private mail on this topic Ithink I'd post my comment on the list:Could we please agree not to post encoded EMail on this list !?!
Thanks,Martin.-- Unix _IS_ user friendly - it's just selective about who its friends are !--___
Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Problem report related to strange splash screens and crashes with certain aircraft

[Arthur Wiebe]

Hey Erik, I may sound like I know what I'm doing sometimes but I really don't. :)Nevertheless I'll add some printf statements and see what happens. I suppose it should be done in the ImageGetRow implementation.
On 11/12/05, Erik Hofman <[EMAIL PROTECTED]> wrote:
Arthur Wiebe wrote:> I think this report basically pins down two of my problems.> First, where spash screens on startup showed up as strange color stipes.> And second, where certain aircraft which define their own spash screen
> crash fgfs.>> I got this report when trying to load the c310 (pre3).> Hopefully either one of you will find what's wrong or I'll look into it> some more tomorrow.Looking at the code I don't see anything abvious.
You might want to add a fw printf() statements in SGTexture::ImageGetRowto see whether the sizes are correct and the pointers are valid.Erik___Flightgear-devel mailing list
Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] OT: FYI, mac os x developers, xcode 2.2 has been released

[Arthur Wiebe]

I've been using Xcode 2.2 for some time now building Flightgear and everything else. Preview builds until now of course.By the way Xcode projects you can use to build PLIB, Simgear, and FlightGear are available now. I've polished them up so they should be ready.
If you're interested I'll commit them to the macflightgear cvs.On 11/12/05, Ima Sudonim <[EMAIL PROTECTED]
> wrote:According to apple developer connection (ADC) news, Apple's xcode 2.2
has been released.It would be nice to know that the new fixes haven't brokenFlightGear... It is an 834 MB disk image update for mac os x 10.4.x. >Download Newly Released Xcode 2.2 Today >Latest tools make building universal binaries even easier.
 >All Apple Developer Connection members can download the newlyreleased Xcode 2.2 at no cost from the ADC Member Site.Basic ADC memberships are free, and permit downloading developmenttools and updates.
ADC members can download from Best regards,Ima
___Flightgear-devel mailing listFlightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d-- - 
http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] diff for browser change for mac os x to use safari

[Arthur Wiebe]

In the macflightgear binary I've been passing "--browser-app=open" to fgfs. This opens the url in the default browser. For me that's Firefox.Your patch could be changed to something like this:Index: FlightGear/src/Main/options
.cxx===RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,vretrieving revision 1.73diff -u -r1.73 options.cxx
--- FlightGear/src/Main/options.cxx     12 Oct 2005 08:55:58-      1.73+++ FlightGear/src/Main/options.cxx     12 Nov 2005 02:41:34 -@@ -172,7 +172,11 @@      fgSetString("/sim/control-mode", "joystick");
      fgSetBool("/sim/auto-coordination", false);#if !defined(WIN32)+#ifdef __APPLE__+    fgSetString("/sim/startup/browser-app", "open");+#else      fgSetString("/sim/startup/browser-app", "netscape");
+#endif#else      fgSetString("/sim/startup/browser-app", "webrun.bat");#endifOn 11/12/05, Ima Sudonim <
[EMAIL PROTECTED]> wrote:Arthur and James,Yes, I agree it's silly, but currently help was broken on my two mac
systems (giving a log message that netscape couldn't be found),followed by a dialog that my browser was started.  It's reallyimportant to me to have browser-based help work on 0.9.9... I forgotthat it was broken until now. (I know I had this working at one
point, and thought I still did as I was building with a modifiedoptions.cxx. I was wrong). I promise to pay much more attention nexttime or at least be conscious when I try these thingsUnfortunately, my fix doesn't work.
I think it should have been the following diff, but as neither diffis working, don't apply them to cvs please.I can't get this options.cxx change working on Mac OS X, I have touse the option --browser-app="open /Applications/Safari.app" when
starting flightgear.Any idea where else /sim/startup/browser-app is set or what (ifanything) is overwriting it?Never mind about the cvs update. It wouldn't break anything even ifapplied, because it didn't work anyway. 8-(
It looks like the mac browser exec actually belongs in gui/gui_funcs.cxx. If I modify void helpCb (puObject *) (line 238) to read: string help_app = "open /Applications/Safari.app" ;//fgGetString
("/sim/startup/browser-app");Safari starts up fine and opens help so this is the spot Arthur wouldneed to pop his code into, I guess.  It would be nice if the returncode from the system call or ShellExecute could be checked before
mkDialog is called.  It's adding insult to injury when your browserhasn't started, but the dialog says it has 8-(I'm still a little confused as to where /sim/startup/browser-app isbeing set, as it doesn't seem to be in main/options.cxx as I expected.
I will leave this to much wiser heads than my own.  Sorry for thetrouble. Some days it doesn't pay to get out of bed in the morning...8-(I'll happily wait for arthur to fix it.Thanks to Arthur and James and all the rest...
ImaIndex: FlightGear/src/Main/options.cxx===RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,vretrieving revision 
1.73diff -u -r1.73 options.cxx--- FlightGear/src/Main/options.cxx 12 Oct 2005 08:55:58-  1.73+++ FlightGear/src/Main/options.cxx 12 Nov 2005 02:41:34 -@@ -172,7 +172,11 @@  fgSetString("/sim/control-mode", "joystick");
  fgSetBool("/sim/auto-coordination", false);#if !defined(WIN32)+#ifdef __APPLE__+fgSetString("/sim/startup/browser-app", "open /Applications/Safari.app");+#else
  fgSetString("/sim/startup/browser-app", "netscape");+#endif#else  fgSetString("/sim/startup/browser-app", "webrun.bat");#endif___
Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] diff for browser change for mac os x to use safari

[Arthur Wiebe]

I agree with James. I've been using the --open-with option for sometime in the mac builds which is set to "open". This opens the url is whatever is the default browser.On 11/12/05, 
James Turner <[EMAIL PROTECTED]> wrote:
On 12 Nov 2005, at 00:58, Ima Sudonim wrote:
With this change, FlightGear on Mac OS X launches the mac os x Safari browser instead of netscape (w/o this change, the browser won't launch without netscape installed, and netscape isn't one of the installed mac os x browsers).
 This approach seems silly - I've got Core Foundation code to launch a URL string via LaunchServices - using whatever browser the user has selected in the system. Hard-coding a browser is always going to annoy people.
I'll post the patch once I dig out the code.H&HJames
___Flightgear-devel mailing listFlightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] Problem report related to strange splash screens and crashes with certain aircraft

[Arthur Wiebe]

I think this report basically pins down two of my problems.First, where spash screens on startup showed up as strange color stipes. And second, where certain aircraft which define their own spash screen crash fgfs.
I got this report when trying to load the c310 (pre3).Hopefully either one of you will find what's wrong or I'll look into it some more tomorrow.Date/Time:  2005-11-11 22:51:12.314 +OS Version: 
10.4.3 (Build 8F46)Report Version: 3Command: fgfsPath:    FlightGear.app/Contents/Resources/fgfsParent:  FlightGear [271]Version: ??? (???)PID:    272Thread: 0Exception:  EXC_BAD_ACCESS (0x0001)
Codes:  KERN_INVALID_ADDRESS (0x0001) at 0x01db7000Thread 0 Crashed:0   <<>>     0x8a60 __memcpy + 704 (cpu_capabilities.h:189)1   libSystem.B.dylib     0x9001a878 fread + 152
2   libz.1.dylib      0x9108d1b0 gzread + 3643   fgfs      0x00104dfc SGTexture::ImageGetRow(SGTexture::_ImageRec*, unsigned char*, int, int) + 2484   fgfs      0x0010601c SGTexture::read_rgb_texture(char const*) + 860
5   fgfs      0x0001bce4 fgSplashInit(char const*) + 17646   fgfs      0x7430 fgMainInit(int, char**) + 13487   fgfs      0x3328 main + 1848   fgfs      0x2acc _start + 344
9   fgfs      0x2970 start + 60Thread 0 crashed with PPC Thread State 64:  srr0: 0x8a60 srr1: 0x0200f030    vrsave: 0xff00    cr: 0x24000220  xer: 0x0004   lr: 0x9001a878  ctr: 0x0040
    r0: 0x   r1: 0xb690   r2: 0x   r3: 0x01db7000    r4: 0x0354ec40   r5: 0x1000   r6: 0x0010   r7: 0x0020    r8: 0x0030   r9: 0x  r10: 0x0060  r11: 0x0080
   r12: 0x01db7000  r13: 0x  r14: 0x  r15: 0x   r16: 0x  r17: 0x  r18: 0x  r19: 0x   r20: 0x  r21: 0x  r22: 0x  r23: 0x
   r24: 0x00016bf0  r25: 0x0001  r26: 0x00016bf0  r27: 0x01db7000   r28: 0xa000e790  r29: 0x6bf0  r30: 0x1000  r31: 0x9001a7f0Binary Images Description:
    0x1000 -   0x754fff fgfs     /Users/arthur/Projects/FlightGearOSX/build/FlightGear/FlightGear.app/Contents/Resources/fgfs 0x184 -  0x18b2fff com.apple.GeForce2MXGLDriver 1.4.16 (4.1.6)    /System/Library/Extensions/GeForce2MXGLDriver.bundle/Contents/MacOS/GeForce2MXGLDriver
 0x18ba000 -  0x18d3fff GLDriver     /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLDriver.bundle/GLDriver 0x18d9000 -  0x18f4fff GLRendererFloat     /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat
 0x1c05000 -  0x1d14fff GLEngine     /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine0x8fe0 - 0x8fe54fff dyld 44.2    /usr/lib/dyld0x9000 - 0x901b3fff libSystem.B.dylib     /usr/lib/libSystem.B.dylib
0x9020b000 - 0x9020 libmathCommon.A.dylib     /usr/lib/system/libmathCommon.A.dylib0x90211000 - 0x90264fff com.apple.CoreText 1.0.1 (???)    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x90291000 - 0x90342fff ATS     /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS0x90371000 - 0x906aefff com.apple.CoreGraphics 1.256.27 (???)    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x9073a000 - 0x90813fff com.apple.CoreFoundation 6.4.4 (368.18)    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation0x9085c000 - 0x9085cfff com.apple.CoreServices 10.4 (???)    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x9085e000 - 0x90960fff libicucore.A.dylib     /usr/lib/libicucore.A.dylib0x909ba000 - 0x90a3efff libobjc.A.dylib     /usr/lib/libobjc.A.dylib0x90a68000 - 0x90ad6fff com.apple.framework.IOKit 1.4 (???)    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90aed000 - 0x90af libauto.dylib     /usr/lib/libauto.dylib0x90b06000 - 0x90dddfff com.apple.CoreServices.CarbonCore 671.2    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x90e43000 - 0x90ec3fff com.apple.CoreServices.OSServices 4.1    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices0x90f0d000 - 0x90f4efff com.apple.CFNetwork
 10.4.3 (129.2)    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork0x90f63000 - 0x90f7bfff com.apple.WebServices 1.1

Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.

[Arthur Wiebe]

OK I found the problem. I hope.In A-10cl-set.xml I removed the following line:  Aircraft/A-10/A-10-splash.rgbAnd it worked. So it seems something is broken in whatever loads these rgb files.
The file does not look corrupted as it opens fine in QuickTime.On 11/11/05, Arthur Wiebe <[EMAIL PROTECTED]
> wrote:I've compiled a list of all the aircraft included in fgfs-base 0.9.9pre3 that do and don't work:
+737-.#A-10cl-A-10cl-A-10fl+bo105+c172p-2dpanel+c172p+c310-yasim+c310dpm-3d-c310-3d
+c310-ifr+c310+c310u3a-jsbsim+c310u3a+Citation-||-f16-3d-f16-mlu-f16-f16at+hunter-2tanks+hunter+j3cub+p51d+pa28-161+ufo+wrightFlyer1903Those with a + work and those with the - do not.
I wonder what .#A-10cl is doing in there as it's invisible for most people.On 11/11/05, Erik Hofman <
[EMAIL PROTECTED]
> wrote:Arthur Wiebe wrote:
> OK,>> But then why when I select the A-10 or f16 fgfs crashes? But when
> selecting the c172p and j3cub there is no problem?The only commonality between the A-10 and f-16 is the turbine sound file??Erik___Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - 
http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.

[Arthur Wiebe]

I've compiled a list of all the aircraft included in fgfs-base 0.9.9pre3 that do and don't work:+737-.#A-10cl-A-10cl-A-10fl+bo105+c172p-2dpanel+c172p+c310-yasim+c310dpm-3d-c310-3d
+c310-ifr+c310+c310u3a-jsbsim+c310u3a+Citation-||-f16-3d-f16-mlu-f16-f16at+hunter-2tanks+hunter+j3cub+p51d+pa28-161+ufo+wrightFlyer1903Those with a + work and those with the - do not.
I wonder what .#A-10cl is doing in there as it's invisible for most people.On 11/11/05, Erik Hofman <[EMAIL PROTECTED]
> wrote:Arthur Wiebe wrote:> OK,>> But then why when I select the A-10 or f16 fgfs crashes? But when
> selecting the c172p and j3cub there is no problem?The only commonality between the A-10 and f-16 is the turbine sound file??Erik___Flightgear-devel mailing list
Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.

[Arthur Wiebe]

OK,But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?I'll do a bit more testing.It almost seems to be a problem with the actual aircraft.
On 11/11/05, Erik Hofman <[EMAIL PROTECTED]> wrote:
Arthur Wiebe wrote:> Now when it comes to debugging stuff like this I'm a newbie.>> When I select the default c172p aircraft everything works fine. But if I> select say the f16 or A-10 then fgfs crashes.
>> Here's the output from gdb.http://www.codecomments.com/archive242-2004-4-170396.html> The problem is gdb.>
> It is the debugger itself that cause the error when stepping instruction.Erik___Flightgear-devel mailing list
Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d
-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.

[Arthur Wiebe]

Now when it comes to debugging stuff like this I'm a newbie.When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes.Here's the output from gdb.
Loading program into debugger…
Program loaded.sharedlibrary apply-load-rules all
Attaching to program: `/Users/arthur/Projects/FlightGearOSX/build/FlightGear/FlightGear.app/Contents/MacOS/FlightGear', process 5516.
mi_cmd_stack_list_frames: Not enough frames in stack.mi_cmd_stack_list_frames: Not enough frames in stack.
I never tested pre1 or pre2 with different aircraft so don't know if I got the error then too.-- - http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Strange colors in spash screen

[Arthur Wiebe]

I wish it was that simple. But it does this no matter what aircraft I select. The only change is in the colors really.Any other mac users with this problem?On 11/11/05, 
Lee Elliott <[EMAIL PROTECTED]> wrote:
On Thursday 10 Nov 2005 18:01, Arthur Wiebe wrote:> http://artooro.spymac.com/pub/fg_spash_screen.png>> This is a screenshot of some very interesting colors I get in
> the splash screen when launching FlightGear 0.9.9-pre2.>> Any idea what could be wrong? It all works fine once> everything has been initiated.>> --> > - 
http://sourceforge.net/users/artooro/> - http://artooro.blogspot.comThat looks like a corrupted splash screen image.  Does it happen
with all the aircraft you've tried?Some aircraft have their own splash image but those that don'tget one of the default splash images.LeeE___
Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] Strange colors in spash screen

[Arthur Wiebe]

http://artooro.spymac.com/pub/fg_spash_screen.pngThis is a screenshot of some very interesting colors I get in the splash screen when launching FlightGear 
0.9.9-pre2.Any idea what could be wrong? It all works fine once everything has been initiated.
-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Bus error SimGear XML Parser - 0.9.9-pre2

[Arthur Wiebe]

Yeah the file is in CVS but it's not included in the 0.9.9-pre2 release base package.I guess I'll just use CVS base then.On 11/10/05, Erik Hofman
 <[EMAIL PROTECTED]> wrote:Arthur Wiebe wrote:
> Here's the output when I try to run fgfs 0.9.9-pre2 with SimGear> 0.3.9-pre2 and 0.9.9-pre2 base package.>> Using Mac OS X hack for initializing C++ stdio...> Error reading properties:
> Failed to open file>  at .//data/cloudlayers.xml>  (reported by SimGear XML Parser)> Bus error>> And of course there's no cloudlayers.xml file.It should be right there in the root of the base package.
Did you upgrade the base package to the CVS version?Erik___Flightgear-devel mailing listFlightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d
-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] Bus error SimGear XML Parser - 0.9.9-pre2

[Arthur Wiebe]

Here's the output when I try to run fgfs 0.9.9-pre2 with SimGear 0.3.9-pre2 and 0.9.9-pre2 base package.Using Mac OS X hack for initializing C++ stdio...Error reading properties: Failed to open file at .//data/cloudlayers.xml
 (reported by SimGear XML Parser)Bus errorAnd of course there's no cloudlayers.xml file.-- 
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Re: FlightGear v0.9.9-pre2

[Arthur Wiebe]

Ima, that problem can be fixed with a small patch to simgear.On 11/10/05, Ima Sudonim <[EMAIL PROTECTED]
> wrote:>Ampere,> A bit off topic: does anyone have success in compiling FlightGear
> and related> libaries using GCC-4.0?I have only one problem, building src/FlightGear/src/Instrumentation/od_gauge.cxx.  I mentioned it in october here:<
http://mail.flightgear.org/pipermail/flightgear-devel/2005-October/039393.html>the workaround is to build just od_gauge.cxx with -fpermissive.I am using:ima% gcc --versionpowerpc-apple-darwin8-gcc-4.0.0
 (GCC) 4.0.0 (Apple Computer, Inc.build 5026)Copyright (C) 2005 Free Software Foundation, Inc.The problem still occurs with latest CVS.Alex,I guess you're not seeing this problem with 4.0.3
? Nice to know it'sbeen fixed! (assuming it's not a private patch) 8-) Now if only applewould update to 4.0.3...best regards,Ima___Flightgear-devel mailing list
Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] Re: Joysticks required? && Universal Binary for OSX

[Arthur Wiebe]

Ignore my question about joysticks and fgfs. Like I said I'm tired and couldn't think straight.Test universal binary 0.9.9pre1 will be coming later this week.On 11/8/05, 
Arthur Wiebe <[EMAIL PROTECTED]> wrote:
Hi ya'llI'm rather tired right now having worked on porting PLIB, Simgear, and FlightGear to Xcode and universal binary for quite some hours.Everything is ported now and I'm pleased with the result. This will make building future releases for mac a lot easier because the automake/autoconf dependencies are gone.
But the main reason for sending this email is when I run fgfs (0.9.9-pre1) I get the following message:Found 0 joystick(s)Can't find any joysticks ...Are joysticks required now? Or maybe something did not build properly? Looking at 
fgfs.cxx it almost looks like joysticks are required.Or maybe plibjs did not build properly and now does not give correct info?Thanks for your response.-- - 

http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] Joysticks required? && Universal Binary for OSX

[Arthur Wiebe]

Hi ya'llI'm rather tired right now having worked on porting PLIB, Simgear, and FlightGear to Xcode and universal binary for quite some hours.Everything is ported now and I'm pleased with the result. This will make building future releases for mac a lot easier because the automake/autoconf dependencies are gone.
But the main reason for sending this email is when I run fgfs (0.9.9-pre1) I get the following message:Found 0 joystick(s)Can't find any joysticks ...Are joysticks required now? Or maybe something did not build properly? Looking at 
fgfs.cxx it almost looks like joysticks are required.Or maybe plibjs did not build properly and now does not give correct info?Thanks for your response.-- - 
http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Mac OS system requirements

[Arthur Wiebe]

Mac OS X 10.332 MB Video Memory256 MB RAM800 MHZ CPUNOTE: The next FlightGear release will require osx 10.4 because some parts don't build with the 10.3.9 SDK. By then most people will have upgraded anyway.
But if not I'm sure we can get it building with the older SDK.On 11/1/05, Curtis L. Olson <[EMAIL PROTECTED]
> wrote:Can someone post the system requirements for running FlightGear?
Mac OS 10.?Minimum 3d hardware?Minimum ram?Thanks,Curt.--Curtis Olsonhttp://www.flightgear.org/~curtHumanFIRST Program  
http://www.humanfirst.umn.edu/FlightGear Project  http://www.flightgear.orgUnique text:2f585eeea02e2c79d7b1d8c4963bae2d___
Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] flightgear cvs & OS X build question

[Arthur Wiebe]

Xcode 2.0 should also be on your Mac OS X 10.4 install cd. But Xcode 2.1 or later is required to build the latest flightgear/simgear/plib cvs.So yes, you need to signup at ADC in order to get it.
On 10/15/05, Thorben <[EMAIL PROTECTED]> wrote:
Hi all,I purchased an Apple iBook G4 and want to run flightgear in OS X 1.4, too. Thething is, I would like to build from cvs, so i went looking for informationand found this:
http://sourceforge.net/docman/display_doc.php?docid=26350&group_id=126825I am not sure if I like signing up at developer.apple.com in order to just getthose xcode stuff...
so, what do you think?ThorbenPS: sorry, this doesn't belong into the developer section stricktly speaking,but as most developers hang around here, i thought it worth a try___
Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] macflightgear info

[Arthur Wiebe]

A Linux version is possible in theory but currently there is some Mac-only C++ code in MacFlightGear and also the source would have to be built manually.Apple is switching to Intel from PowerPC processors and universal binary simply allows apps to run native on both arcs. This apps are optimized for both and the only downside is that the file sizes are about twice the size.
On 9/28/05, Jim Wilson <[EMAIL PROTECTED]> wrote:
> From: Arthur Wiebe>> There are some other mac fgfs guys on this list. I figured I'd let everyone know exactly what the MacOSX port of FGFS is up to.>> 
http://artooro.blogspot.com/2005/09/mac-flightgear-project-report.html>> (NOTE:)> The Flight starter (fgrun equiv) is referred to as MacFlightGear and the rest is obvious (I hope).> We're not using fgrun because first, it won't compile at all on OSX without major changes, and second, even if it did work it would look ugly because it uses FLTK so a port isn't worthwhile. While I wouldn't care, a lot of mac users would care about how it looks.
> MacFlightGear uses the wxWidgets framework.>> Also a note to you mac developers, if you would be interested in helping make fgfs more user-friendly drop me a line. I would love to have more guys join. We're reaching 4 downloads in the next week or so by the way. Probably nothing compared to others but to me it means, get to work!
> http://macflightgear.sourceforge.netThe wxWidgets/gtk apps I've used seem to work pretty well,  so it might actually be possible to have a version easily portable to linux.  I'm not able to do any development at the moment,  but if you need a tester before releasing,  I'm willing to mess around with it for a while on the little ibook.  I wonder what kind of performance hit you are talking about using the "universal binary" mode?  Anyway, thanks for the update.
Best,Jim___Flightgear-devel mailing listFlightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d-- - 
http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] macflightgear info

[Arthur Wiebe]

There are some other mac fgfs guys on this list. I figured I'd let everyone know exactly what the MacOSX port of FGFS is up to.http://artooro.blogspot.com/2005/09/mac-flightgear-project-report.html
(NOTE:)The Flight starter (fgrun equiv) is referred to as MacFlightGear and the rest is obvious (I hope).We're not using fgrun because first, it won't compile at all on OSX without major changes, and second, even if it did work it would look ugly because it uses FLTK so a port isn't worthwhile. While I wouldn't care, a lot of mac users would care about how it looks.
MacFlightGear uses the wxWidgets framework.Also a note to you mac developers, if you would be interested in helping make fgfs more user-friendly drop me a line. I would love to have more guys join. We're reaching 4 downloads in the next week or so by the way. Probably nothing compared to others but to me it means, get to work!
http://macflightgear.sourceforge.net-- - http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear icon

[Arthur Wiebe]

Great job Josh.An .icns file (used by OSX) is available here in case somebody wants it:http://artooro.spymac.net/images/fgfs.icnsIt contains 128,48,32, and 16 versions + bit masks for < 48.
Thanks!On 9/20/05, Josh Babcock <[EMAIL PROTECTED]> wrote:
Josh Babcock wrote:> I will go ahead and do a 32, 48, 64 and 128 px version of mine, though I> have to say that the 48 px one looks great. Maybe it would be a better> choice for the larger ones. Of course, there's nothing stopping us from
> including multiple options for icons.>> Josh>> ___> Flightgear-devel mailing list> 
Flightgear-devel@flightgear.org> http://mail.flightgear.org/mailman/listinfo/flightgear-devel> 2f585eeea02e2c79d7b1d8c4963bae2d
>Ta-Da!http://jrbabcock.home.comcast.net/flightgear/icons/index.htmlJosh___
Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear icon

[Arthur Wiebe]

Sounds alright.I need a 128x128 for MacOSX and so will probably create one based off of your images.On 9/20/05, Josh Babcock <
[EMAIL PROTECTED]> wrote:Frederic Bouvier wrote:> Arthur Wiebe a écrit :
>>> I am working on a new mac flightgear binary because of all the>> problems people have with the current release and want to use a better>> icon this time.>>>> Is there any official logo or something I should base it off?
>>>> There is no official logo that fit in the 32x32 area imposed by Windows,> but I like the one provided by Josh and grabbed it for the Win32 build>> 
http://jrbabcock.home.comcast.net/flightgear/scripts/flightgear.gif>> It is a 16x16 so I resize it ( Josh, if you have a better 32x32 version,> I would be glad to use it instead ).>> There is a nice 48x48 here :
> ftp://ftp.ihg.uni-duisburg.de/FlightGear/Devel/fgfs-jims-icon.bmp, but> unusable after downsizing.>> -Fred>
>>>>> ___> Flightgear-devel mailing list> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel> 2f585eeea02e2c79d7b1d8c4963bae2d>As soon as I have a free moment, I will re-make this at 32x32. It was a
simple process, and I still remember it. What sizes do various Linuxdesktop systems use? I think they tend to be bigger icons. I don't know,I use X, but only as a place to open my aterm window :) While I'm at it
I could make some of them as well, and we could throw them all in thebase package.Josh___Flightgear-devel mailing list
Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d
-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] configure error

[Arthur Wiebe]

Hi Adam.I knew of that method of fixing this problem but just didn't think of it for some odd reason. Things are sure odd these days.  :)Thanks for the tip.The strage thing though is that it always worked before for me even with fgfs source.
By the way there are some build instructions which are located at:<http://sourceforge.net/docman/display_doc.php?docid=26350&group_id=126825
>It's part of the documentation linked to from http://macflightgear.sourceforge.netIt probably needs to be updated or improved in some areas. If you are so inclined you could join the macflightgear project and help out. Contact me about that.
Thanks.On 9/20/05, Adam Dershowitz <[EMAIL PROTECTED]> wrote:
This is a known problem with building FlightGear on a Mac.  For somereason autogen for FG does not copy them, while it works fine forSimGear.  I have not been able to figure out why it happens, or whatis different about FG and SG, but I wrote some Mac build instructions
that have a work around.  Here is the relevant part:* Build FlightGear > cd $BUILDDIR/src/source > ./autogen.shAutomake should do the next two steps, but for some reason does notfor 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
 > makeDoes anyone know if my Mac build instructions were ever included inany documentation anywhere?  Best I can tell, the only Mac buildinstructions are very old, out of date, and don't work at all.
Instead they just lead newbies off in a completely wrong direction.--AdamOn Sep 20, 2005, at 8:14 AM, Arthur Wiebe wrote:> With fresh copy is still is a nogo.>> In case it helps here's the output of 
autogen.sh:>> Host info: Darwin Power Macintosh>  automake: 1.6.3 (16)>> Running aclocal> Running autoheader> Running automake --add-missing> 
configure.ac <http://configure.ac> : installing `./install-sh'> configure.ac <http://configure.ac> : installing `./mkinstalldirs'
> configure.ac <http://configure.ac> : installing `./missing'> Makefile.am <
http://Makefile.am> : installing `./INSTALL'> Makefile.am <http://Makefile.am> : installing `./COPYING'> src/AIModel/Makefile.am: installing `./depcomp'
> Running autoconf>> Does not look like anything is wrong. I can't figure it out because> I've> never had problems like this before.>>> On 9/20/05, Arthur Wiebe < [EMAIL PROTECTED]>> [EMAIL PROTECTED]> wrote:>> The file is not present and like I said before I did run autogen.sh.
> Using autoconf 2.59.>> I'll try a fresh copy of the source and see what happens.>>>> On 9/20/05, Erik Hofman <[EMAIL PROTECTED] [EMAIL PROTECTED]> >> wrote:>> Arthur Wiebe wrote:>>> I just checked our the latest flightgear source and after running>> autogen.sh
 tried to run configure but got the following error:>> configure: error: cannot run /bin/sh ./config.sub>>>> Is this file present?> If not you need to run autogen.sh>> If so, you should make sure it's marked executable:
> chmod +x config.sub>> Erik>>> ___> Flightgear-devel mailing list> Flightgear-devel@flightgear.org
 Flightgear-> [EMAIL PROTECTED]>>>  <
http://mail.flightgear.org/mailman/listinfo/flightgear-devel>> http://mail.flightgear.org/mailman/listinfo/flightgear-devel> 2f585eeea02e2c79d7b1d8c4963bae2d
>>>>>> --> > -  <http://sourceforge.net/users/artooro/>> 
http://sourceforge.net/users/artooro/> -  <http://artooro.blogspot.com> http://artooro.blogspot.com>>>
>> --> > - http://sourceforge.net/users/artooro/> <http://sourceforge.net/users/artooro/
>> - http://artooro.blogspot.com <http://artooro.blogspot.com>>> >
___Flightgear-devel mailing listFlightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d-- - 
http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] FlightGear icon

[Arthur Wiebe]

I am working on a new mac flightgear binary because of all the problems people have with the current release and want to use a better icon this time.Is there any official logo or something I should base it off?
-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] configure error

[Arthur Wiebe]

With fresh copy is still is a nogo.In case it helps here's the output of autogen.sh:Host info: Darwin Power Macintosh automake: 1.6.3 (16)Running aclocalRunning autoheaderRunning automake --add-missing
configure.ac: installing `./install-sh'configure.ac: installing `./mkinstalldirs'configure.ac: installing `./missing'
Makefile.am: installing `./INSTALL'Makefile.am: installing `./COPYING'src/AIModel/Makefile.am: installing `./depcomp'Running autoconf
Does not look like anything is wrong. I can't figure it out because I've never had problems like this before.On 9/20/05, Arthur Wiebe <
[EMAIL PROTECTED]> wrote:The file is not present and like I said before I did run 
autogen.sh.Using autoconf 2.59.I'll try a fresh copy of the source and see what happens.On 9/20/05, 

Erik Hofman <[EMAIL PROTECTED]> wrote:

Arthur Wiebe wrote:> I just checked our the latest flightgear source and after running> autogen.sh tried to run configure but got the following error:> configure: error: cannot run /bin/sh ./config.sub
Is this file present?If not you need to run autogen.shIf so, you should make sure it's marked executable:chmod +x config.subErik___

Flightgear-devel mailing listFlightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - 
http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com

-- - http://sourceforge.net/users/artooro/- http://artooro.blogspot.com

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] configure error

[Arthur Wiebe]

The file is not present and like I said before I did run autogen.sh.Using autoconf 2.59.I'll try a fresh copy of the source and see what happens.On 9/20/05, 
Erik Hofman <[EMAIL PROTECTED]> wrote:
Arthur Wiebe wrote:> I just checked our the latest flightgear source and after running> autogen.sh tried to run configure but got the following error:> configure: error: cannot run /bin/sh ./config.sub
Is this file present?If not you need to run autogen.shIf so, you should make sure it's marked executable:chmod +x config.subErik___
Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d-- - http://sourceforge.net/users/artooro/- 
http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] configure error

[Arthur Wiebe]

I just checked our the latest flightgear source and after running autogen.sh tried to run configure but got the following error:configure: error: cannot run /bin/sh ./config.sub
Not being very familiar with the autoconf system I decided to write about the problem here instead of trying to fix it.-- - 
http://sourceforge.net/users/artooro/- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Build Problem Under MacOS 10.4

[Arthur Wiebe]

Did you use GCC 4 or 3.3? I've been so busy that I've not even tried
building FGFS on 10.4. I did try to build plib but it failed with the
same type of error. And I fixed it just like you (except by making it
non-static) but then a mess of other errors showed up that well... I
knew nothing about.On 5/20/05, Jonathan Polley <[EMAIL PROTECTED]> wrote:
For some reason, the c172_aero.c file in src/FDM/LaRCsim generates alink error.  There is a variable, called simply 'b' that conflictswith a symbol in MacOS 10.4's OpenGL library (go figure).  Withoutmaking it static (or changing its name), I get the following link error:
ld: ../../src/FDM/LaRCsim/libLaRCsim.a(c172_aero.o) illegal referenceto symbol: _b defined in indirectly referenced dynamic library /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
For now, I have made the 'b' variable static and then FlightGearlinks just fine.  It does not complete its initialization, but Iprobably have a messed up config file (it has been a while since Ihave build FlightGear).
Jonathan Polley___Flightgear-devel mailing listFlightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d-- - http://artooro.blogspot.com
  (Weblog)- http://sourceforge.net/users/artooro/
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear BitTorrents

[Arthur Wiebe]

Martin, BitTorrent could eliminate the need for multiple mirrors
altogether. Conventional servers have their place, but take X-Plane
for example: 
The BitTorrent download is displayed as the preferred download method,
but for those who would rather download from a conventional server
there is room for that as well.
While 200 kbps is fast enough under most circumstances, I have noticed
that the servers are still slow. (The time it takes to connect and at
times download)
BitTorrent is scalable. The more people downloading, the faster it gets.
But I do see your point.

Frederic, you would manage the versions just as it is done now.

By the way, the FGFS category is:
http://www.open-bits.org/browse.php?cat=64335

If nobody is really interested in this, I won't maintain it in the future.

On Thu, 17 Mar 2005 11:50:41 +0100, Frederic Bouvier <[EMAIL PROTECTED]> wrote:
> Quoting Martin Spott :
> 
> > I have the whole set but I don't volunteer because I personally don't
> > feel that we're going to gain noticeable improvement just by offering
> > another file transfer method.
> 
> And what about version management on a P2P network ?
> What is the version of file w090n40.tgz ?
> 
> -Fred
> 
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://sourceforge.net/users/artooro/

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear BitTorrents

[Arthur Wiebe]

Yes, getting the entire scenery available via bittorrent would be
great. (As long as there are seeders)
But it's huge, and would take some work.

On Tue, 15 Mar 2005 17:19:23 -0800, Vandewalle, David E
<[EMAIL PROTECTED]> wrote:
> Good idea!
> 
> Now what would be really neat is if we could get some seeders started
> with the entire world scenery distribution.
> Things that size (i.e. HUGE!) is where bit torrent can really shine.
> 
> I would volunteer, but I don't have the entire set ...
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Arthur
> Wiebe
> Sent: Tuesday, March 15, 2005 2:24 PM
> To: FlightGear developers discussions; FlightGear user discussions
> Subject: [Flightgear-devel] FlightGear BitTorrents
> 
> Hey everyone,
> 
> FlightGear (source and base), and SimGear source are now available for
> download via BitTorrent, thanks to http://www.open-bits.org
> 
> See:
> http://www.open-bits.org/browse.php?cat=3
> http://www.open-bits.org/details.php?id=902 (SimGear Source)
> http://www.open-bits.org/details.php?id=901 (fgfs-base)
> http://www.open-bits.org/details.php?id=900 (FlightGear source)
> 
> For those who don't know what BitTorrent is, see
> http://www.bittorrent.com/introduction.html
> And you can download the client from http://www.bittorrent.com
> 
> Currently we need seeders. So even though I'm very sure most if not all
> of you already have the above releases, you can still seed for those who
> don't :)
> 
> Curtis, Maybe you might want to link to the torrents on the download
> page? I have no idea what kind of load you have on your servers but this
> may sure help to reduce it.
> 
> Thanks, and enjoy! (And happy seeding)
> --
> 
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://sourceforge.net/users/artooro/

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] FlightGear BitTorrents

[Arthur Wiebe]

Hey everyone,

FlightGear (source and base), and SimGear source are now available for
download via BitTorrent, thanks to http://www.open-bits.org

See:
http://www.open-bits.org/browse.php?cat=3
http://www.open-bits.org/details.php?id=902 (SimGear Source)
http://www.open-bits.org/details.php?id=901 (fgfs-base)
http://www.open-bits.org/details.php?id=900 (FlightGear source)

For those who don't know what BitTorrent is, see
http://www.bittorrent.com/introduction.html
And you can download the client from http://www.bittorrent.com

Currently we need seeders. So even though I'm very sure most if not
all of you already have the above releases, you can still seed for
those who don't :)

Curtis, Maybe you might want to link to the torrents on the download
page? I have no idea what kind of load you have on your servers but
this may sure help to reduce it.

Thanks, and enjoy! (And happy seeding)
-- 


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Compiling Flightgear 0.9 from CVS on Mac OS X

[Arthur Wiebe]

I don't know if anyone is aware of this but a document on building
from source for Mac OS X is located at
http://sourceforge.net/docman/display_doc.php?docid=26350&group_id=126825

And for myself, I upgraded autoconf and automake in order to run
autogen.sh from the FGFS CVS. For some reason Apple's versions don't
work.

On Thu, 3 Mar 2005 08:35:00 -, Giles Robertson
<[EMAIL PROTECTED]> wrote:
> > g++  -g -O2 -D_REENTRANT  -L/FlightGear/lib -o test-up  test-up.o
> > -lsgmath -lsgxml -lsgmisc -lsgdebug -lsgstructure -lsgtiming
> > -lplibsg -lplibul -lz
> > ld: can't locate file for: -lsgmath
> > make[1]: *** [test-up] Error 1
> > make: *** [all-recursive] Error 1
> 
> That's failed to find the first SimGear library. Check that you
> installed (make install) SimGear after you built it, and that
> ./configure has detected the directory where it's installed.
> 
> Giles Robertson
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://sourceforge.net/users/artooro/

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear compilation problem

[Arthur Wiebe]

On Mac OS X, to fix this you must change GL/glut.h to GLUT/glut.h and
it should work again.

Yes I know it shouldn't be like that but Apple does crazy things.

On Mon, 28 Feb 2005 08:38:59 +0100, Horst J. Wobig <[EMAIL PROTECTED]> wrote:
> Brian Topping wrote:
> 
> > make[1]: Entering directory `/home/topping/dev/unix/FlightGear/tests'
> > if gcc -DHAVE_CONFIG_H -I. -I. -I../src/Include   -I/usr/X11R6/include
> > -I/usr/local//include  -g -O2 -D_REENTRANT -MT est-epsilon.o -MD -MP -MF
> > ".deps/est-epsilon.Tpo" -c -o est-epsilon.o est-epsilon.c; \
> > then mv -f ".deps/est-epsilon.Tpo" ".deps/est-epsilon.Po"; else rm -f
> > ".deps/est-epsilon.Tpo"; exit 1; fi
> > est-epsilon.c:13:19: GL/glut.h: No such file or directory
> 
> well, glut is missing. On my system (SuSE 9.0/9.1) the header file is
> /usr/include/GL/glut.h (GLUT = OpenGL Utility Toolkit). Normally comes
> together with OpenGL. You need the devel-packages (.h - files) in
> addition to the runtime files (libraries) [if fedora makes this
> distinction] to compile OpenGL/GLUT sources.
> 
> HJW
> 
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://sourceforge.net/users/artooro/

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Mac os x simgear build break with RenderTexture.cpp

[Arthur Wiebe]

That's what happens when you don't read the whole thing. :)


On Mon, 31 Jan 2005 16:03:25 -0800, Adam Dershowitz
<[EMAIL PROTECTED]> wrote:
> Don't you mean it should not include it with Windows?
> Since it is #ifndef not #ifdef?
> 
> -- Adam
> 
> > From: Arthur Wiebe <[EMAIL PROTECTED]>
> > Reply-To: FlightGear developers discussions 
> > 
> > Date: Mon, 31 Jan 2005 18:46:07 -0500
> > To: FlightGear developers discussions 
> > Subject: Re: [Flightgear-devel] Mac os x simgear build break with
> > RenderTexture.cpp
> >
> > That is wierd. Because of this:
> >
> > #ifndef _WIN32
> > #  include SG_GLX_H
> > #endif
> >
> > It should only include GLX on Windows.
> >
> > On Mon, 31 Jan 2005 17:51:34 -0500, [EMAIL PROTECTED]
> > <[EMAIL PROTECTED]> wrote:
> >>
> >> When I went to do a full build of simgear January 27th, I am having a
> >> problem with the build of RenderTexture.cpp.  I have been unable to
> >> download newer source since then due to a network problem that  breaks
> >> CVS on my local network.
> >>
> >> Mac OS X doesn't generally support glx.h
> >>
> >> If someone has X11 developer sources installed on mac os x, the glx
> >> file exists on:
> >>
> >> /usr/X11R6/include/GL
> >>
> >> but I don't think that I should be using that GLX file as I am NOT
> >> building a version of FG for X, but rather for native mac os x.
> >>
> >> Does anyone have any suggestions for how to build simgear/screen
> >> without requiring GLX? (I tried explicitly giving --without-x during
> >> configure but it didn't seem to help).
> >>
> >> The first error message is:
> >>
> >> g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../..
> >> -DGLX_GLXEXT_PROTOTYPES
> >> -I/Users/ima/Desktop/FlightGear/fgdev9.8/include  -g -O2 -D_REENTRANT
> >> -c -o RenderTexture.o `test -f 'RenderTexture.cpp' || echo
> >> './'`RenderTexture.cpp
> >> In file included from RenderTexture.cpp:58:
> >> ../../simgear/screen/RenderTexture.h:56:20: OpenGL/glx.h: No such file
> >> or directory
> >>
> >> .. followed by these errors
> >>
> >> In file included from RenderTexture.cpp:58:
> >> ../../simgear/screen/RenderTexture.h:342: error: 'GLXContext' is used
> >> as a
> >> type, but is not defined as a type.
> >> ../../simgear/screen/RenderTexture.h:343: error: 'GLXPbuffer' is used
> >> as a
> >> type, but is not defined as a type.
> >> ../../simgear/screen/RenderTexture.h:345: error: 'GLXDrawable' is used
> >> as a
> >> type, but is not defined as a type.
> >> ../../simgear/screen/RenderTexture.h:346: error: 'GLXContext' is used
> >> as a
> >> type, but is not defined as a type.
> >> RenderTexture.cpp: In constructor `RenderTexture::RenderTexture(const
> >> char*)':
> >> RenderTexture.cpp:127: error: class `RenderTexture' does not have any
> >> field
> >> named `_hGLContext'
> >> RenderTexture.cpp:128: error: class `RenderTexture' does not have any
> >> field
> >> named `_hPBuffer'
> >>   .. and so on
> >>
> >> Sorry, I seem especially clueless lately. 8-(
> >> TIA for any help!
> >>
> >> Best regards,
> >>
> >> Ima
> >>
> >> ___
> >> Flightgear-devel mailing list
> >> Flightgear-devel@flightgear.org
> >> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>
> >
> >
> > --
> > 
> > - http://artooro.blogspot.com  (Weblog)
> > - http://machcms.sourceforge.net  (MachCMS Project)
> > - http://acalproj.sourceforge.net  (Calendar Project)
> > 
> > ___
> > Flightgear-devel mailing list
> > Flightgear-devel@flightgear.org
> > http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> > 2f585eeea02e2c79d7b1d8c4963bae2d
> 
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Mac os x simgear build break with RenderTexture.cpp

[Arthur Wiebe]

That is wierd. Because of this:

#ifndef _WIN32
#  include SG_GLX_H
#endif

It should only include GLX on Windows.

On Mon, 31 Jan 2005 17:51:34 -0500, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> 
> When I went to do a full build of simgear January 27th, I am having a
> problem with the build of RenderTexture.cpp.  I have been unable to
> download newer source since then due to a network problem that  breaks
> CVS on my local network.
> 
> Mac OS X doesn't generally support glx.h
> 
> If someone has X11 developer sources installed on mac os x, the glx
> file exists on:
> 
> /usr/X11R6/include/GL
> 
> but I don't think that I should be using that GLX file as I am NOT
> building a version of FG for X, but rather for native mac os x.
> 
> Does anyone have any suggestions for how to build simgear/screen
> without requiring GLX? (I tried explicitly giving --without-x during
> configure but it didn't seem to help).
> 
> The first error message is:
> 
> g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../..
> -DGLX_GLXEXT_PROTOTYPES
> -I/Users/ima/Desktop/FlightGear/fgdev9.8/include  -g -O2 -D_REENTRANT
> -c -o RenderTexture.o `test -f 'RenderTexture.cpp' || echo
> './'`RenderTexture.cpp
> In file included from RenderTexture.cpp:58:
> ../../simgear/screen/RenderTexture.h:56:20: OpenGL/glx.h: No such file
> or directory
> 
> .. followed by these errors
> 
> In file included from RenderTexture.cpp:58:
> ../../simgear/screen/RenderTexture.h:342: error: 'GLXContext' is used
> as a
> type, but is not defined as a type.
> ../../simgear/screen/RenderTexture.h:343: error: 'GLXPbuffer' is used
> as a
> type, but is not defined as a type.
> ../../simgear/screen/RenderTexture.h:345: error: 'GLXDrawable' is used
> as a
> type, but is not defined as a type.
> ../../simgear/screen/RenderTexture.h:346: error: 'GLXContext' is used
> as a
> type, but is not defined as a type.
> RenderTexture.cpp: In constructor `RenderTexture::RenderTexture(const
> char*)':
> RenderTexture.cpp:127: error: class `RenderTexture' does not have any
> field
> named `_hGLContext'
> RenderTexture.cpp:128: error: class `RenderTexture' does not have any
> field
> named `_hPBuffer'
>   .. and so on
> 
> Sorry, I seem especially clueless lately. 8-(
> TIA for any help!
> 
> Best regards,
> 
> Ima
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] link to my homepage

[Arthur Wiebe]

That may a good idea.

But just so you all know and so you'll hopefully calm down, the file
has been removed from the distribution although there is still "a note
from the packager" and future releases will not even have that.

So please forget this whole thing, because if you don't I'll post the
entire file on how to get to Heaven in this thread. :)
Maybe I should anyways just in case you don't know. Well if you want
to know you can just email me.


On Sat, 22 Jan 2005 16:36:27 -0500, Ampere K. Hardraade
<[EMAIL PROTECTED]> wrote:
> Perhaps it will be a good idea to put up a notice that says "FlightGear is not
> responsible for the contents of external websites".
> 
> Ampere
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear 0.9.8, Mac OS X build

[Arthur Wiebe]

All arguments are currently being processed internally (As in my
head.) Hopefully tomorrow will bring a peaceful resolution.

Currently, the distro is being updated and if you would like to
contact me, send me a direct email.

On Thu, 20 Jan 2005 20:12:57 -, Jim Wilson <[EMAIL PROTECTED]> wrote:
> Arthur Wiebe said:
> 
> > I am not a religious person but do believe Jesus Christ meant it when
> > he said "Go ye into all the world, and preach the gospel to every
> > creature" and saw this as another potential medium.
> 
> Did he also say "Go ye into the world and tell people you aren't religious
> when you are"?  Don't be bashful about your beliefs, but
Religious:
   1.  Having or showing belief in and reverence for God or a deity.
   2. Of, concerned with, or teaching religion: a religious text.
   3. Extremely scrupulous or conscientious: religious devotion to duty.

n. pl. religious
A member of a monastic order, especially a nun or monk. 

I am religious if you see it as the first definition, but there are
many ways religion is interpreted.
I am not a Catholic or "Christian", but a believer in Jesus Christ. I
do not follow a religion but the word of God which is the Bible, which
is not a religion but a faith.
> 
> >
> > What I will do and am in the process of doing is update the package to
> > include this in an About.rtf file:
> >
> > "The following contents have been included by Arthur Wiebe and may not
> > reflect the views of any of the contributors or developers of the
> > FlightGear project."
> >
> > O hope that satisfies this issue.
> 
> ..do be mindful of the diversity here, even if you believe you are right and
> just want to help others.  This isn't the right way to do it.  Any sort of
> religious statement or even political statement would be received in a similar
> fashion.  The flightgear project is really just about flight simulation and
> that is all that makes this a community.  Would it be ok to just remove the
> message from the distribution?
> 
> Best,
> 
> Jim

> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Re: FlightGear 0.9.8, Mac OS X build

[Arthur Wiebe]

On Thu, 20 Jan 2005 20:38:32 +0100, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> * Arthur Wiebe -- Thursday 20 January 2005 20:24:
> > What I will do and am in the process of doing is update the package to
> > include this in an About.rtf file:
> >
> > "The following contents have been included by Arthur Wiebe and may not
> > reflect the views of any of the contributors or developers of the
> > FlightGear project."
> >
> > O hope that satisfies this issue.
> 
> No, it doesn't. But as long as there are no links to this package from
> the official FlightGear page, there isn't much we can do against this
> abuse. *If* FlightGear officially links to this package, then I will
> stop contributing to it.
> 
> m.

Now I must say that you are acting childish.

> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear 0.9.8, Mac OS X build

[Arthur Wiebe]

Hi Everyone,

In case you don't know I'm the one who created the distribution in question.

First of all I believe that the contents of the RTF file should be
welcomed by everyone, and I also believe they are true.
But I also realize that it may be harmful to this project by turning
people away from it.

I am not a religious person but do believe Jesus Christ meant it when
he said "Go ye into all the world, and preach the gospel to every
creature" and saw this as another potential medium.

What I will do and am in the process of doing is update the package to
include this in an About.rtf file:

"The following contents have been included by Arthur Wiebe and may not
reflect the views of any of the contributors or developers of the
FlightGear project."

O hope that satisfies this issue.
I also believe the Bible when it says, "If it be possible, as much as
lieth in you, live peaceably with all men."

By the way I am also going to fix the permissions issue at the same time.

On Thu, 20 Jan 2005 19:51:08 +0100, Durk Talsma <[EMAIL PROTECTED]> wrote:
> Curt wrote:
> >I suggest that we try (as much as possible) to stay focused on building
> >flight simulators.  If we diverge into a heated discussion of religion
> >(or politics, or text editors, or operating systems, etc.) we are just
> >going to hate each other at the end of the day, and we will be much less
> >effective as a leading open source project.
> 
> Martin Spott wrote:
> > view point, it's just that he chose a medium to carry his opinion that
> > is totally unacceptable.
> >
> 
> In my opinion, both arguments clearly express why a religious document should
> not be part of an official FlightGear distribution. Not even necesarily
> because it's religious. It's off-topic and therefore unprofessional.
> 
> Cheers,
> Durk
> 
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Announce v0.9.8

[Arthur Wiebe]

Yes, it was added after 0.9.8-pre2


On Wed, 19 Jan 2005 15:20:43 -0800, Adam Dershowitz
<[EMAIL PROTECTED]> wrote:
> Damn, so I missed one of those fixes.
> 
> Actually, I just checked, and that file was not present when I was building
> and patching for GL location, so it has been added since, and was done the
> "old" way instead.
> 
> Can one of you guys with CVS access fix that one?
> 
> Thanks,
> 
> -- Adam
> 
> > From: Arthur Wiebe <[EMAIL PROTECTED]>
> > Reply-To: FlightGear developers discussions 
> > 
> > Date: Wed, 19 Jan 2005 17:56:52 -0500
> > To: FlightGear developers discussions 
> > Subject: Re: [Flightgear-devel] Announce v0.9.8
> >
> > Hey Adam,
> >
> > I had to make one small change.
> > Hopefully the attached patch answers your question.
> >
> > But other than that it all built ok.
> >
> > On Wed, 19 Jan 2005 14:37:36 -0800, Adam Dershowitz
> > <[EMAIL PROTECTED]> wrote:
> >> I have not yet had a chance to build 0.9.8, so I am curious if it built 
> >> just
> >> fine "right out of the box"?  And do my Mac build instructions hold up OK
> >> for this version?
> >>
> >> Thanks for building and posting the Mac bin.
> >>
> >> -- Adam
> >>
> >>> From: Arthur Wiebe <[EMAIL PROTECTED]>
> >>> Reply-To: FlightGear developers discussions
> >>> 
> >>> Date: Wed, 19 Jan 2005 16:43:53 -0500
> >>> To: FlightGear developers discussions 
> >>> Subject: Re: [Flightgear-devel] Announce v0.9.8
> >>>
> >>> The Mac OS X package is now available from
> >>> http://macflightgear.sourceforge.net/
> >>>
> >>> I wrote a small wxPython app which is included. For now it allows you
> >>> to choose the aircraft and airport. (Because I plain can't get fgrun
> >>> ported to OS X)
> >>>
> >>>
> >>> On Wed, 19 Jan 2005 21:22:23 -, Jim Wilson <[EMAIL PROTECTED]> wrote:
> >>>> Thomas Förster said:
> >>>>
> >>>>> Am Mittwoch 19 Januar 2005 15:40 schrieb Jim Wilson:
> >>>>>> Erik Hofman said:
> >>>>>>> Curtis L. Olson wrote:
> >>>>>>>> I have finalized the v0.9.8 release and rolled up the source and base
> >>>>>>>> packages, updated the web site, and made the new files available on 
> >>>>>>>> the
> >>>>>>>> ftp site.  Everyone should be clear to start building binary versions
> >>>>>>>> for their favorite platforms.
> >>>>>>>
> >>>>>>> FlightGear binaries can be found at the usual place:
> >>>>>>> http://www.1stweb.nl/~ehofman/fgfs/
> >>>>>>
> >>>>>> I'm building a set of binaries on top of Yoper and have been wondering
> >>>>>> about distrubiting them.  They (probably) will work (and I'd like to 
> >>>>>> find
> >>>>>> out for sure if there are any volunteers) on recent releases of rpm
> >>>>>> systems
> >>>>>> (Fedora C3, Mandrake 10.x, maybe even Suse 9.2.  I'd like are 
> >>>>>> suggestions
> >>>>>> as far as where these can be posted.  I just don't have the bandwidth
> >>>>>> here.
> >>>>>
> >>>>> I can help with Fedora C3.
> >>>>>
> >>>>> Thomas
> >>>>
> >>>> Hi Thomas,
> >>>>
> >>>> The files are here:
> >>>> http://www.spiderbark.com/oneshot/
> >>>>
> >>>> If you already have downloaded the base package you can skip downloading 
> >>>> my
> >>>> rpm and just move it to /usr/share/FlightGear/data.   fgrun is not 
> >>>> actually
> >>>> checking for the base package dependeency.
> >>>>
> >>>> Let me know how you make out.
> >>>>
> >>>> In case you don't know, if you have plib and simgear already installed on
> >>>> this
> >>>> machine you need to remove them or move them out of the way...just to 
> >>>> avoid
> >>>> conflicts.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Jim
> >>>>
> >>>>
> &

Re: [Flightgear-devel] Announce v0.9.8

[Arthur Wiebe]

Hey Adam,

I had to make one small change.
Hopefully the attached patch answers your question.

But other than that it all built ok.

On Wed, 19 Jan 2005 14:37:36 -0800, Adam Dershowitz
<[EMAIL PROTECTED]> wrote:
> I have not yet had a chance to build 0.9.8, so I am curious if it built just
> fine "right out of the box"?  And do my Mac build instructions hold up OK
> for this version?
> 
> Thanks for building and posting the Mac bin.
> 
> -- Adam
> 
> > From: Arthur Wiebe <[EMAIL PROTECTED]>
> > Reply-To: FlightGear developers discussions 
> > 
> > Date: Wed, 19 Jan 2005 16:43:53 -0500
> > To: FlightGear developers discussions 
> > Subject: Re: [Flightgear-devel] Announce v0.9.8
> >
> > The Mac OS X package is now available from
> > http://macflightgear.sourceforge.net/
> >
> > I wrote a small wxPython app which is included. For now it allows you
> > to choose the aircraft and airport. (Because I plain can't get fgrun
> > ported to OS X)
> >
> >
> > On Wed, 19 Jan 2005 21:22:23 -, Jim Wilson <[EMAIL PROTECTED]> wrote:
> >> Thomas Förster said:
> >>
> >>> Am Mittwoch 19 Januar 2005 15:40 schrieb Jim Wilson:
> >>>> Erik Hofman said:
> >>>>> Curtis L. Olson wrote:
> >>>>>> I have finalized the v0.9.8 release and rolled up the source and base
> >>>>>> packages, updated the web site, and made the new files available on the
> >>>>>> ftp site.  Everyone should be clear to start building binary versions
> >>>>>> for their favorite platforms.
> >>>>>
> >>>>> FlightGear binaries can be found at the usual place:
> >>>>> http://www.1stweb.nl/~ehofman/fgfs/
> >>>>
> >>>> I'm building a set of binaries on top of Yoper and have been wondering
> >>>> about distrubiting them.  They (probably) will work (and I'd like to find
> >>>> out for sure if there are any volunteers) on recent releases of rpm 
> >>>> systems
> >>>> (Fedora C3, Mandrake 10.x, maybe even Suse 9.2.  I'd like are suggestions
> >>>> as far as where these can be posted.  I just don't have the bandwidth 
> >>>> here.
> >>>
> >>> I can help with Fedora C3.
> >>>
> >>> Thomas
> >>
> >> Hi Thomas,
> >>
> >> The files are here:
> >> http://www.spiderbark.com/oneshot/
> >>
> >> If you already have downloaded the base package you can skip downloading my
> >> rpm and just move it to /usr/share/FlightGear/data.   fgrun is not actually
> >> checking for the base package dependeency.
> >>
> >> Let me know how you make out.
> >>
> >> In case you don't know, if you have plib and simgear already installed on
> >> this
> >> machine you need to remove them or move them out of the way...just to avoid
> >> conflicts.
> >>
> >> Thanks,
> >>
> >> Jim
> >>
> >>
> >> ___
> >> Flightgear-devel mailing list
> >> Flightgear-devel@flightgear.org
> >> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>
> >
> >
> > --
> > 
> > - http://artooro.blogspot.com  (Weblog)
> > - http://machcms.sourceforge.net  (MachCMS Project)
> > - http://acalproj.sourceforge.net  (Calendar Project)
> >
> > ___
> > Flightgear-devel mailing list
> > Flightgear-devel@flightgear.org
> > http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> > 2f585eeea02e2c79d7b1d8c4963bae2d
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)


patch
Description: Binary data
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Announce v0.9.8

[Arthur Wiebe]

The Mac OS X package is now available from
http://macflightgear.sourceforge.net/

I wrote a small wxPython app which is included. For now it allows you
to choose the aircraft and airport. (Because I plain can't get fgrun
ported to OS X)


On Wed, 19 Jan 2005 21:22:23 -, Jim Wilson <[EMAIL PROTECTED]> wrote:
> Thomas Förster said:
> 
> > Am Mittwoch 19 Januar 2005 15:40 schrieb Jim Wilson:
> > > Erik Hofman said:
> > > > Curtis L. Olson wrote:
> > > > > I have finalized the v0.9.8 release and rolled up the source and base
> > > > > packages, updated the web site, and made the new files available on 
> > > > > the
> > > > > ftp site.  Everyone should be clear to start building binary versions
> > > > > for their favorite platforms.
> > > >
> > > > FlightGear binaries can be found at the usual place:
> > > > http://www.1stweb.nl/~ehofman/fgfs/
> > >
> > > I'm building a set of binaries on top of Yoper and have been wondering
> > > about distrubiting them.  They (probably) will work (and I'd like to find
> > > out for sure if there are any volunteers) on recent releases of rpm 
> > > systems
> > > (Fedora C3, Mandrake 10.x, maybe even Suse 9.2.  I'd like are suggestions
> > > as far as where these can be posted.  I just don't have the bandwidth 
> > > here.
> >
> > I can help with Fedora C3.
> >
> > Thomas
> 
> Hi Thomas,
> 
> The files are here:
> http://www.spiderbark.com/oneshot/
> 
> If you already have downloaded the base package you can skip downloading my
> rpm and just move it to /usr/share/FlightGear/data.   fgrun is not actually
> checking for the base package dependeency.
> 
> Let me know how you make out.
> 
> In case you don't know, if you have plib and simgear already installed on this
> machine you need to remove them or move them out of the way...just to avoid
> conflicts.
> 
> Thanks,
> 
> Jim
> 
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Individual aircraft downloads

[Arthur Wiebe]

You can also lower the quality of PNG image as well as up the
compression level. Doing so can make PNG's smaller than JPEG's.

For example a top quality JPEG has a larger file size than a best quality PNG.

So I don't know what you use to create the PNG's but you should be
able to edit these settings.

On Mon, 17 Jan 2005 16:03:06 -0600, Curtis L. Olson
<[EMAIL PROTECTED]> wrote:
> A fair point ... I'll take care of it ...
> 
> Curt.
> 
> 
> Paul Surgeon wrote:
> 
> >I don't want to sound like someone who likes to nitpik but ...   :)
> >
> >Is there any good reason to use PNGs for the thumbnails?
> >There will be 60 aircraft thumbnails and we are averaging about 32K per
> >thumbnail at the moment even with max PNG compression.
> >That equates to nearly 2MB just for thumbnails.
> >JPG can do it in 360K at 85% quality (average of 6KB per thumbnail) with no
> >visual difference to the naked eye.
> >
> >I know PNG is lossless and JPG is evil because it's not LGPL but I think it's
> >the right tool for the job (photos on web pages).
> >
> >Some of us don't have the luxury/option of high speed Internet connections 
> >and
> >a 2MB web page takes 6 minutes to download on a 64K line.
> >
> >Paul
> >
> >On Monday, 17 January 2005 20:49, Curtis L. Olson wrote:
> >
> >
> >>For the upcoming release of FG, I'm working on a couple scripts to
> >>create/manage a web page for individual downloads.  Here is where I'm at
> >>so far.  There is plenty room for improvement, but this will at least
> >>get us started:
> >>
> >>http://www.flightgear.org/Downloads/aircraft/
> >>
> >>If aircraft developers put a 171x128 pixel image in the top aicraft
> >>directory called "thumbnail.png", this will automatically get picked up
> >>and put on the web page.  There's no need to get these all populated
> >>before the v0.9.8 image, but it would be great if people could start
> >>filling thes in with nice pictures.  The one's I created can be replaced
> >>if someone comes up with something better.
> >>
> >>Aircraft developers can continue to use our base package cvs, or they
> >>can maintain their files locally and submit a ready to install .tgz
> >>package ... either way will work fine.
> >>
> >>As part of this, I hope to significantly trim down the default base
> >>package.
> >>
> >>There are obvious areas of improvement such as categorizing the aircraft
> >>and putting them in their own sections (and we should do that
> >>eventually) but this at least is a workable starting point for this
> >>release.
> >>
> >>Regards,
> >>
> >>Curt.
> >>
> >>
> >
> >___
> >Flightgear-devel mailing list
> >Flightgear-devel@flightgear.org
> >http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >2f585eeea02e2c79d7b1d8c4963bae2d
> >
> >
> 
> --
> 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
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Google adwords?

[Arthur Wiebe]

One thing that you might want to consider is that the clickthough rate
is really low. And is it really worth it.
I've been using AdSense for awhile now and the clickthough rate, at
least for me is very low on average. An average of 0.5%. That's with
about 4000 impressions.

On Thu, 13 Jan 2005 20:28:02 -, Jim Wilson <[EMAIL PROTECTED]> wrote:
> "Curtis L. Olson" said:
> 
> > Dumb question: do we want to investigate the possibility of adding
> > google adds to the FlightGear site?  Is this out of bounds, or within
> > bounds for an open-source project.  It's a potential revenue generator,
> > but it's unclear if it will generate $0.39 per month or $39.00 per month
> > or $390.00 per month.
> >
> > As I understand it, we create a space on our page, and google puts
> > whatever they want there, but they try to be as relevant to our page as
> > their algorithms will let them.  Supposedly we have ways to block
> > "competitor's" adds in case (for instance) we don't want MSFS adds to
> > show up on our page.
> >
> > Is this worth looking into, or would it be crossing some sort of
> > open-source ethical line?
> >
> 
> It probably is, because high ethical standards are fundamental to the
> open-source concept.  A few general ethical issues along those lines:
> 
> - more commercial appearance to site.
> - ads are not particularly effective for advertisers (compared to adwords on
> the google search engine pages), but they make a lot of money for Google.
> - the content being linked to is not necessarily on the up and up.  Google
> does not screen new advertisers like aol and overture do.  So ads for snake
> oil and free software with spy/adware can show up.  Just do a google search on
> "viagra" or "baldness" and you'll see what I mean.
> 
> You could add a couple more items to the cdrom page and call it a "Store" like
> Mozilla does.  PostGres runs their own ads, but not on the home page and only
> one per page.  It seems prudent to look at other high profile projects
> (Flightgear is getting there!) and try not to stand out to much in the area of
> commercialization.  Google might be easy,  but if there is an option that
> might be a little more work (and better) I'd be glad to help out (rather than
> just being a nay sayer ;-)).
> 
> One good thing might be just a "Donations" link like a lot of oss web sites
> show.  Make sure that it is clear that even small donations are appreciated
> (so that folks don't think they can't afford it).
> 
> Best,
> 
> Jim
> 
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] FlightGear more popular than X-Plane?

[Arthur Wiebe]

Could it be possible that FlightGear is more popular than X-Plane on Mac OS X?

Take a look at the included screenshot. I recently added the port from
http://macflightgear.sourceforge.net to Apple Downloads and it seems
people like it for some reason.

While I prefer X-Plane myself I assume it's popularity is due to being
free and open source.

 - And some of you though I was a troll once, LOL.
<>___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Individual aircraft downloads

[Arthur Wiebe]

Actually, I think *.tar.gz is more popular that *.tgz.
And makes more sense than .tgz. But it's really a trivial thing.
Anyway you go will work.


On Mon, 03 Jan 2005 18:58:51 -0600, Curtis L. Olson
<[EMAIL PROTECTED]> wrote:
> Oliver C. wrote:
> 
> >Could you change the file format from *.tgz to *.tar.gz?
> >
> >I ask because *.tgz is used by Slackware as a package format (it's a tar.gz
> >file with a install script in it) and this is leading to confusion
> >when you have Slackware *.tgz files and *.tgz files that are no Slackware
> >packages on your harddrive.
> >
> >So file endings called *.tar.gz would be much better than *.tgz.
> >
> >
> 
> .tgz is a little bit better understood on the win/mac platforms than
> .tar.gz, and if I remember my slackware, a slackware .tgz file is the
> exact same format as a .tar.gz ... the reason slackware called their
> packages .tgz is to facilitate downloading and managing them on windows
> systems ...
> 
> Regards,
> 
> 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
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear v0.9.8-pre2

[Arthur Wiebe]

Oh, was I complaining? Just forget it then. I guess nobody else cares
that it takes more than a few minutes just to connect to the server. I
won't either.


On Mon, 3 Jan 2005 21:44:44 + (UTC), Martin Spott
<[EMAIL PROTECTED]> wrote:
> Arthur Wiebe wrote:
> > The FTP mirrors are really slow! Has the thought of using BitTorrent
> > for source releases crossed anyone's mind? If you need help I can.
> 
> To my knowledge you're the only one who is complaining - right ?
> Which bandwidth do you expect ?
> 
> Martin.
> --
>  Unix _IS_ user friendly - it's just selective about who its friends are !
> --
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear v0.9.8-pre2

[Arthur Wiebe]

The FTP mirrors are really slow! Has the thought of using BitTorrent
for source releases crossed anyone's mind? If you need help I can.


On Mon, 03 Jan 2005 14:43:39 -0600, Curtis L. Olson
<[EMAIL PROTECTED]> wrote:
> The second v0.9.8 prerelease of FlightGear (v0.9.8-pre2) is now
> available for download and testing (source only.)
> 
> http://www.flightgear.org
> 
> I ask as many people as possible to download the tarballs, build and
> test.  The more problems we can catch now, the less problems our end
> users will catch.
> 
> Best regards,
> 
> 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
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] New project at SF.net, macflightgear. Flightgear Mac OS X

[Arthur Wiebe]

In response to comments in the recent Mac OS X thread, I have
registered a new project at Sourceforge.net:
http://sourceforge.net/projects/macflightgear/
http://macflightgear.sf.net

I have done nothing with it yet (It just got accepted).

I am now calling for anyone here who wants to join.

Here are the goals for this project:
1) Make FlightGear user friendly on Mac OS X.
2) Either port fgrun to Mac OS X or write a native application to
include with our package.

Email me at
artooro AT users DOT sourceforge DOT net
if you would like to join. Tell me what you would like to do and give
your Sourceforge.net username.
As soon as I have time I'll get the ball rolling.

(And please don't throw flames at me for  needlessly starting a
project just for this.)

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

OK, I guess I do crazy things when without knowledge. :)

The time_t error went away when including time.h, but login_tty() is
still undefined.

Looking in the login_tty manual page it says you need to include it with:
#include 

So I added that include at the top of fgrun_pty.cxx but it still doesn't work.


On Sat, 18 Dec 2004 21:49:29 +0100, Frederic Bouvier <[EMAIL PROTECTED]> wrote:
> Arthur Wiebe wrote :
> 
> >if g++ -DHAVE_CONFIG_H -I. -I. -I.   -I/FlightGear/include  -g -O2 -MT
> >fgrun_pty.o -MD -MP -MF ".deps/fgrun_pty.Tpo" \
> >  -c -o fgrun_pty.o `test -f 'fgrun_pty.cxx' || echo './'`fgrun_pty.cxx; \
> >then mv -f ".deps/fgrun_pty.Tpo" ".deps/fgrun_pty.Po"; \
> >else rm -f ".deps/fgrun_pty.Tpo"; exit 1; \
> >fi
> >In file included from fgrun_pty.cxx:32:
> >/usr/include/utmp.h:75: error: 'time_t' is used as a type, but is not defined
> >   as a type.
> >make[2]: *** [fgrun_pty.o] Error 1
> >make[1]: *** [all] Error 2
> >make: *** [all-recursive] Error 1
> >
> >A quick look in utmp.h and I see time_t defined there like this:
> >
> >
> time_t is defined in time.h . If utmp.h doesn't include it already, add
> this line *before* utmp.h :
> 
> #include 
> 
> -Fred
> 
> ___
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

entClass
_GetEventDispatcherTarget
_GetEventKind
_GetEventParameter
_GetFlavorData
_GetFlavorDataSize
_GetFlavorFlags
_GetMainDevice
_GetMainEventLoop
_GetMenuHandle
_GetMenuItemRefCon
_GetMouse
_GetNextDevice
_GetNumEventsInQueue
_GetQDGlobalsArrow
_GetQDGlobalsScreenBits
_GetResource
_GetScrapFlavorData
_GetScrapFlavorSize
_GetScriptManagerVariable
_GetWindowBounds
_GetWindowClass
_GetWindowEventTarget
_GlobalToLocal
_HiliteMenu
_InstallEventHandler
_InstallEventLoopTimer
_InstallReceiveHandler
_InstallTrackingHandler
_InvalWindowRect
_InvalWindowRgn
_IsWindowActive
_IsWindowCollapsed
_KeyTranslate
_LocalToGlobal
_MoreMasters
_MoveWindow
_NewAEEventHandlerUPP
_NewEventHandlerUPP
_NewEventLoopTimerUPP
_PostEventToQueue
_PutScrapFlavor
_QuitApplicationEventLoop
_ReleaseEvent
_RepositionWindow
_RunApplicationEventLoop
_SelectWindow
_SendEventToEventTarget
_SetEventLoopTimerNextFireTime
_SetEventMask
_SetFrontProcess
_SetItemMark
_SetOrigin
_SetPort
_SetPortClipRegion
_SetWTitle
_SetWindowClass
_SizeWindow
_GetCursor
_SetCursor
_ClosePoly
_CopyRgn
_FrameRect
_GetRegionBounds
_KillPoly
_Line
_LineTo
_MoveTo
_OpenPoly
_PaintPoly
_PaintRect
_RectInRgn
_SectRgn
_SetEmptyRgn
_SetRect
_DrawText
_FMSwapFont
_FontMetrics
_GetFNum
_GetFontInfo
_TextFace
_TextFont
_TextSize
_TextWidth
_GetPixBaseAddr
_AddDragItemFlavor
_ConvertEventRefToEventRecord
_DisposeDrag
_NewDrag
_TrackDrag
_FrameArc
_PaintArc
_FrameOval
_PaintOval
_SetUserFocusWindow
_PenPat
_PenSize
make[2]: *** [fgrun] Error 1
make[1]: *** [all] Error 2
make: *** [all-recursive] Error 1

So now it's something about undefined symbols. Could that have
anything to do with time_t? :)

It almost seems easier just to write your own app, the one I wrote is
rather primitive though.

On Sat, 18 Dec 2004 17:10:49 +0100, Frederic Bouvier <[EMAIL PROTECTED]> wrote:
> As far as I know, there is no fgrun list, so post here.
> 
> it looks like your implementation of termios.h is incomplete.
> 
> try changing the line :
> 
> term.c_oflag &= ~( OLCUC | ONLCR );
> 
> by
> 
> term.c_oflag &= ~ONLCR;
> 
> -Fred
> 
> Arthur Wiebe wrote :
> 
> >Should I post it here or in the fgrun mailing list? I assume here
> >since there's only one person subscribed to the fgrun list.
> >
> >I was getting this error:
> >
> >if g++ -DHAVE_CONFIG_H -I. -I. -I.   -I/FlightGear/include  -g -O2 -MT
> >run_posix.o -MD -MP -MF ".deps/run_posix.Tpo" \
> >  -c -o run_posix.o `test -f 'run_posix.cxx' || echo './'`run_posix.cxx; \
> >then mv -f ".deps/run_posix.Tpo" ".deps/run_posix.Po"; \
> >else rm -f ".deps/run_posix.Tpo"; exit 1; \
> >fi
> >run_posix.cxx: In member function `void Wizard::run_fgfs()':
> >run_posix.cxx:61: error: `OLCUC' undeclared (first use this function)
> >run_posix.cxx:61: error: (Each undeclared identifier is reported only once 
> >for
> >   each function it appears in.)
> >make[2]: *** [run_posix.o] Error 1
> >make[1]: *** [all] Error 2
> >make: *** [all-recursive] Error 1
> >
> >I looked the relevant code which is this:
> >
> >void
> >Wizard::run_fgfs()
> >{
> >pid_t pid;
> >int master = -1;
> >
> >#if defined(HAVE_TERMIOS_H)
> >struct termios term;
> >    tcgetattr( STDOUT_FILENO, &term );
> >term.c_oflag &= ~( OLCUC | ONLCR ); // This is the error line,
> >something with the OLCUC constant
> >
> >pid = pty_fork( &master, 0, &term, 0 );
> >#else
> >pid = pty_fork( &master, 0, 0, 0 );
> >#endif
> >
> >And I program in PHP and some other, this is just a little too
> >different for me to figure out how to fix.
> >
> >
> >On Sat, 18 Dec 2004 14:34:02 +0100, Frederic Bouvier <[EMAIL PROTECTED]> 
> >wrote:
> >
> >
> >>Arthur Wiebe wrote :
> >>
> >>
> >>
> >>>I couldn't get fgrun to compile on OSX and so have started to write
> >>>one that's OS X native using Cocoa and AppleScript. (Applescript
> >>>Studio)
> >>>
> >>>
> >>>
> >>You should try to share your experience / problems with fgrun in order
> >>to get help. I can check your patches if you have some.
> >>
> >>-Fred
> >>
> >>
> 
> ___
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

Should I post it here or in the fgrun mailing list? I assume here
since there's only one person subscribed to the fgrun list.

I was getting this error:

if g++ -DHAVE_CONFIG_H -I. -I. -I.   -I/FlightGear/include  -g -O2 -MT
run_posix.o -MD -MP -MF ".deps/run_posix.Tpo" \
  -c -o run_posix.o `test -f 'run_posix.cxx' || echo './'`run_posix.cxx; \
then mv -f ".deps/run_posix.Tpo" ".deps/run_posix.Po"; \
else rm -f ".deps/run_posix.Tpo"; exit 1; \
fi
run_posix.cxx: In member function `void Wizard::run_fgfs()':
run_posix.cxx:61: error: `OLCUC' undeclared (first use this function)
run_posix.cxx:61: error: (Each undeclared identifier is reported only once for 
   each function it appears in.)
make[2]: *** [run_posix.o] Error 1
make[1]: *** [all] Error 2
make: *** [all-recursive] Error 1

I looked the relevant code which is this:

void
Wizard::run_fgfs()
{
pid_t pid;
int master = -1;

#if defined(HAVE_TERMIOS_H)
struct termios term;
tcgetattr( STDOUT_FILENO, &term );
term.c_oflag &= ~( OLCUC | ONLCR ); // This is the error line,
something with the OLCUC constant

pid = pty_fork( &master, 0, &term, 0 );
#else
pid = pty_fork( &master, 0, 0, 0 );
#endif

And I program in PHP and some other, this is just a little too
different for me to figure out how to fix.


On Sat, 18 Dec 2004 14:34:02 +0100, Frederic Bouvier <[EMAIL PROTECTED]> wrote:
> Arthur Wiebe wrote :
> 
> >I couldn't get fgrun to compile on OSX and so have started to write
> >one that's OS X native using Cocoa and AppleScript. (Applescript
> >Studio)
> >
> You should try to share your experience / problems with fgrun in order
> to get help. I can check your patches if you have some.
> 
> -Fred
> 
> ___
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

My package actually does not use a .fgfsrc file. It passes the flags
straight to fgfs.
And I don't understand resource forks either. And have never worked with them.

I couldn't get fgrun to compile on OSX and so have started to write
one that's OS X native using Cocoa and AppleScript. (Applescript
Studio)
Right now you can select the aircraft but that's it. Although it's working.
If it works out good it could be used in future binary packages. No
more messing with the Terminal, but with all it's advantages.

On Fri, 17 Dec 2004 23:05:57 -0600, Jonathan Polley <[EMAIL PROTECTED]> wrote:
> Double-clicking the icon isn't the problem.  In many cases, getting the
> .fgfsrc file properly installed was the problem.  For my next release,
> I was going to include a python script that would set up the file and
> modify the default resource file.  Many Mac users that subscribe to the
> Users mailing list are not UNIX literate.  This is a problem for me
> since I am use to dealing with UNIX types and don't know how to write
> for a person who isn't.  It really is a change in thinking.
> 
> 
> Jonathan Polley
> 
> 
> On Dec 17, 2004, at 6:09 PM, Arthur Wiebe wrote:
> 
> > lol, How many different ways can you explain to somebody how to double
> > click an icon.
> >
> >
> > On Fri, 17 Dec 2004 18:07:26 -0600, Jonathan Polley
> > <[EMAIL PROTECTED]> wrote:
> >> That is not necessarily the case.  I have had a heck of a time
> >> explaining to users how to get the application to run.
> >>
> >> On Dec 17, 2004, at 6:04 PM, Arthur Wiebe wrote:
> >>
> >>> It's a single application in a disk image. No instructions included.
> >>> I
> >>> figured anyone downloading FlightGear would know what to do with it.
> >>>
> >>> By the way Curt, it's done uploading.
> >>>
> >>> On Fri, 17 Dec 2004 17:50:23 -0600, Jonathan Polley
> >>> <[EMAIL PROTECTED]> wrote:
> >>>> Arthur,
> >>>>
> >>>>  Considering the problems some people have been having in
> >>>> running
> >>>> the Mac version, have you added instructions to the .dmg file?  I
> >>>> was
> >>>> able to host the previous version (0.9.6) on my .mac account, but it
> >>>> was less than 125 MB (which is my limit).
> >>>
> >>> 0.9.6 is the current version is it not?
> >>> My package is built from CVS 2004-12-17 so I named the version
> >>> 0.9.6+.
> >>>
> >>>>
> >>>> Jonathan Polley
> >>>>
> >>>> On Friday, December 17, 2004, at 03:56PM, Arthur Wiebe
> >>>> <[EMAIL PROTECTED]> wrote:
> >>>>
> >>>>> I have built an application bundle of FlightGear for Mac OS X.
> >>>>> It's a
> >>>>> rather large application because it includes everything such as the
> >>>>> base data, fgfs, etc. Compressed it's a total of 132 MB.
> >>>>>
> >>>>> I have no place to host such large files so I've made it available
> >>>>> via
> >>>>> BitTorrent. I've attached it to this email.
> >>>>> Hopefully we can get some more people seeding.
> >>>>>
> >>>>> Now it would be really nice if you could switch aircraft from in
> >>>>> the
> >>>>> simulator! :)
> >>>>> --
> >>>>> 
> >>>>>
> >>>>> ___
> >>>>> Flightgear-devel mailing list
> >>>>> [EMAIL PROTECTED]
> >>>>> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >>>>> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>>>>
> >>>>
> >>>> Of COURSE they can do that.  They're engineers!
> >>>>
> >>>> ___
> >>>> Flightgear-devel mailing list
> >>>> [EMAIL PROTECTED]
> >>>> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >>>> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>>>
> >>>
> >>>
> >>> --
> >>> 
> >>> - http://artooro.blogspot.com  (Weblog)
> >>> - http://machcms.sourceforge.net  (MachCMS Project)
> >>> - http://acalproj.sourceforge.net  (Calendar Projec

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

On Sat, 18 Dec 2004 01:43:04 +0100, Arnt Karlsen <[EMAIL PROTECTED]> wrote:
> On Fri, 17 Dec 2004 16:55:26 -0500, Arthur wrote in message
> <[EMAIL PROTECTED]>:
> 
> > I have built an application bundle of FlightGear for Mac OS X. It's a
> > rather large application because it includes everything such as the
> > base data, fgfs, etc. Compressed it's a total of 132 MB.
> >
> > I have no place to host such large files
> 
> ...so sign up with SourceForge or somesuch:
> http://sourceforge.net/account/newuser_emailverify.php
> 
> .AFAICTF
> http://sourceforge.net/docman/display_doc.php?group_id=1&docid=6048
> your bundle is acceptable at SourceForge.net.
I'm an active SF.net user and administrator of two projects there. I
didn't think simply a package of another product would be worth a new
project though, there is GIMP-App
> 
> --
> ..med vennlig hilsen = with Kind Regards from Arnt... ;-)
> ...with a number of polar bear hunters in his ancestry...
>   Scenarios always come in sets of three:
>   best case, worst case, and just in case.
> 
> ___
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

Ok. I'll include instructions in the next version.
Right now I'm trying to get fgrun going on Mac OS X and maybe include
that in the next version as well if it's good.

So far fgrun doesn't look like it's going to work.

On Fri, 17 Dec 2004 16:13:13 -0800, Adam Dershowitz
<[EMAIL PROTECTED]> wrote:
> I agree.  That first time was not at all clear.
> It would be great to include some instructions as well, or many people just
> won't get it.
> 
> -- Adam
> 
> > From: Jonathan Polley <[EMAIL PROTECTED]>
> > Reply-To: FlightGear developers discussions 
> > <[EMAIL PROTECTED]>
> > Date: Fri, 17 Dec 2004 18:07:26 -0600
> > To: FlightGear developers discussions <[EMAIL PROTECTED]>
> > Subject: Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle
> > Available
> >
> > That is not necessarily the case.  I have had a heck of a time
> > explaining to users how to get the application to run.
> >
> > On Dec 17, 2004, at 6:04 PM, Arthur Wiebe wrote:
> >
> >> It's a single application in a disk image. No instructions included. I
> >> figured anyone downloading FlightGear would know what to do with it.
> >>
> >> By the way Curt, it's done uploading.
> >>
> >> On Fri, 17 Dec 2004 17:50:23 -0600, Jonathan Polley
> >> <[EMAIL PROTECTED]> wrote:
> >>> Arthur,
> >>>
> >>>  Considering the problems some people have been having in running
> >>> the Mac version, have you added instructions to the .dmg file?  I was
> >>> able to host the previous version (0.9.6) on my .mac account, but it
> >>> was less than 125 MB (which is my limit).
> >>
> >> 0.9.6 is the current version is it not?
> >> My package is built from CVS 2004-12-17 so I named the version 0.9.6+.
> >>
> >>>
> >>> Jonathan Polley
> >>>
> >>> On Friday, December 17, 2004, at 03:56PM, Arthur Wiebe
> >>> <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> I have built an application bundle of FlightGear for Mac OS X. It's a
> >>>> rather large application because it includes everything such as the
> >>>> base data, fgfs, etc. Compressed it's a total of 132 MB.
> >>>>
> >>>> I have no place to host such large files so I've made it available
> >>>> via
> >>>> BitTorrent. I've attached it to this email.
> >>>> Hopefully we can get some more people seeding.
> >>>>
> >>>> Now it would be really nice if you could switch aircraft from in the
> >>>> simulator! :)
> >>>> --
> >>>> 
> >>>>
> >>>> ___
> >>>> Flightgear-devel mailing list
> >>>> [EMAIL PROTECTED]
> >>>> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >>>> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>>>
> >>>
> >>> Of COURSE they can do that.  They're engineers!
> >>>
> >>> ___
> >>> Flightgear-devel mailing list
> >>> [EMAIL PROTECTED]
> >>> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >>> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>>
> >>
> >>
> >> --
> >> 
> >> - http://artooro.blogspot.com  (Weblog)
> >> - http://machcms.sourceforge.net  (MachCMS Project)
> >> - http://acalproj.sourceforge.net  (Calendar Project)
> >>
> >> ___
> >> 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
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

lol, How many different ways can you explain to somebody how to double
click an icon.


On Fri, 17 Dec 2004 18:07:26 -0600, Jonathan Polley <[EMAIL PROTECTED]> wrote:
> That is not necessarily the case.  I have had a heck of a time
> explaining to users how to get the application to run.
> 
> On Dec 17, 2004, at 6:04 PM, Arthur Wiebe wrote:
> 
> > It's a single application in a disk image. No instructions included. I
> > figured anyone downloading FlightGear would know what to do with it.
> >
> > By the way Curt, it's done uploading.
> >
> > On Fri, 17 Dec 2004 17:50:23 -0600, Jonathan Polley
> > <[EMAIL PROTECTED]> wrote:
> >> Arthur,
> >>
> >>  Considering the problems some people have been having in running
> >> the Mac version, have you added instructions to the .dmg file?  I was
> >> able to host the previous version (0.9.6) on my .mac account, but it
> >> was less than 125 MB (which is my limit).
> >
> > 0.9.6 is the current version is it not?
> > My package is built from CVS 2004-12-17 so I named the version 0.9.6+.
> >
> >>
> >> Jonathan Polley
> >>
> >> On Friday, December 17, 2004, at 03:56PM, Arthur Wiebe
> >> <[EMAIL PROTECTED]> wrote:
> >>
> >>> I have built an application bundle of FlightGear for Mac OS X. It's a
> >>> rather large application because it includes everything such as the
> >>> base data, fgfs, etc. Compressed it's a total of 132 MB.
> >>>
> >>> I have no place to host such large files so I've made it available
> >>> via
> >>> BitTorrent. I've attached it to this email.
> >>> Hopefully we can get some more people seeding.
> >>>
> >>> Now it would be really nice if you could switch aircraft from in the
> >>> simulator! :)
> >>> --
> >>> 
> >>>
> >>> ___
> >>> Flightgear-devel mailing list
> >>> [EMAIL PROTECTED]
> >>> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >>> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>>
> >>
> >> Of COURSE they can do that.  They're engineers!
> >>
> >> ___
> >> Flightgear-devel mailing list
> >> [EMAIL PROTECTED]
> >> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >> 2f585eeea02e2c79d7b1d8c4963bae2d
> >>
> >
> >
> > --
> > 
> > - http://artooro.blogspot.com  (Weblog)
> > - http://machcms.sourceforge.net  (MachCMS Project)
> > - http://acalproj.sourceforge.net  (Calendar Project)
> >
> > ___
> > 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
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

It's a single application in a disk image. No instructions included. I
figured anyone downloading FlightGear would know what to do with it.

By the way Curt, it's done uploading.

On Fri, 17 Dec 2004 17:50:23 -0600, Jonathan Polley <[EMAIL PROTECTED]> wrote:
> Arthur,
> 
>  Considering the problems some people have been having in running the Mac 
> version, have you added instructions to the .dmg file?  I was able to host 
> the previous version (0.9.6) on my .mac account, but it was less than 125 MB 
> (which is my limit).

0.9.6 is the current version is it not?
My package is built from CVS 2004-12-17 so I named the version 0.9.6+.

> 
> Jonathan Polley
> 
> On Friday, December 17, 2004, at 03:56PM, Arthur Wiebe <[EMAIL PROTECTED]> 
> wrote:
> 
> >I have built an application bundle of FlightGear for Mac OS X. It's a
> >rather large application because it includes everything such as the
> >base data, fgfs, etc. Compressed it's a total of 132 MB.
> >
> >I have no place to host such large files so I've made it available via
> >BitTorrent. I've attached it to this email.
> >Hopefully we can get some more people seeding.
> >
> >Now it would be really nice if you could switch aircraft from in the
> >simulator! :)
> >--
> >
> >
> >___
> >Flightgear-devel mailing list
> >[EMAIL PROTECTED]
> >http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> >2f585eeea02e2c79d7b1d8c4963bae2d
> >
> 
> Of COURSE they can do that.  They're engineers!
> 
> ___
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
> 


-- 

- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] FlightGear Mac OS X Application Bundle Available

[Arthur Wiebe]

I have built an application bundle of FlightGear for Mac OS X. It's a
rather large application because it includes everything such as the
base data, fgfs, etc. Compressed it's a total of 132 MB.

I have no place to host such large files so I've made it available via
BitTorrent. I've attached it to this email.
Hopefully we can get some more people seeding.

Now it would be really nice if you could switch aircraft from in the
simulator! :)
-- 



FlightGear-0.9.6+.dmg.torrent
Description: Binary data
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] FlightGear not compatible with autoconf 1.57

[Arthur Wiebe]

I just checked out the latest source from CVS and ran autogen.sh. Then
when trying to run configure I got the following error:
configure: error: cannot run /bin/sh ./config.sub

After upgrading to autoconf 1.59 there were some warnings when running
autogen.sh but at least configure works.

I'm pretty sure it's version 1.57 or 1.56 of autoconf that had this problem.
-- 


___
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]

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

[Arthur Wiebe]

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

[Arthur Wiebe]

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 Wiebe]

Now.

I have built FlightGear on Mac OS X. After a LOT of trial and error
building SimGear and FlightGear without the X11 SDK.

It seems all that needed to be done was change GL/gl.h and GL/glu.h in
all the source files which contained those includes to OpenGL/*.

What needs to be done is to make a patch that include GL/* on other
systems but OpenGL/* on Mac OS X. I believe this would make compiling
SimGear and FlightGear on Mac OS X pain less.
I had to make, make clean, make again in order to find all the
problems.  A patch is coming!

So, next I'll be making a Mac OS X package of FlightGear, and make a
double-clickable application for it.

On Sat, 13 Nov 2004 12:35:26 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote:
> If I recall correctly. OpenAL was required for PLIB. And it is not
> included in Panther although it will be in Tiger. Maybe that should be
> added?
> 
> 
> 
> 
> On Fri, 12 Nov 2004 09:12:43 -0800, Adam Dershowitz
> <[EMAIL PROTECTED]> wrote:
> > OK,
> > I took a whack at drafting up a new set of Mac build instructions for the
> > users guide.  I would appreciate it if someone else could try to run through
> > this step by step just to confirm that I did not miss anything (another set
> > of eyes and a different computer is pretty useful for checking.).
> >
> > Arthur, since you are trying a bunch, perhaps you can start completely from
> > scratch and just follow through these instructions step by step.  It might
> > help you and it might help get them checked.
> >
> > Anyway, I hope this is helpful.  If anyone has any other edits or
> > suggestions I would be happy to hear them or just pass them directly to
> > Martin.
> >
> > --Adam
> >
> > And here are is the new procedure:
> >
> > How to build FlightGear v0.9.6 on Mac OS X.
> >
> > These steps worked fine for me, but I don't know if other OS versions etc.
> > might also work:
> > Mac OS 10.3.6
> > XCode 1.5
> > By default this included gcc 3.3, autotmake 1.6.3, autoconf 2.53, so
> > nothing else is required.
> >
> > * Setup the build environment:
> > Create the directory to build into, and one for the source.  For example:
> > mkdir FlightGear
> > mkdir FlightGear/src
> > then I like to just create an environment variable to this:
> > export BUILDDIR=/where/ever/you/created/FlightGear
> >
> > * Download PLIB
> > I first tried to use plib 1.8.3 but that will not compile properly on a Mac
> > without a few changes.  But, as of this writing, the CVS version will.
> > You can either use CVS, or grab the snapshot from here:
> > http://plib.sourceforge.net/dist/current.tgz
> >
> > If you open the above link it should automatically unpack to create a folder
> > called plib.
> > Drag (or copy) that folder into /where/ever/you/created/FlightGear/src
> >
> > * Build PLIB
> >
> > > cd $BUILDDIR/src/plib
> > > ./autogen.sh
> > > ./configure --prefix=$BUILDDIR
> > > make install
> >
> > * Get SimGear sources
> >
> > > cd $BUILDDIR/src
> > >
> > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.3 login
> > # Enter "guest" for password
> > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.3 -z3 co
> > SimGear
> >
> > * Build SimGear
> >
> > > cd $BUILDDIR/src/SimGear
> > > ./autogen.sh
> > > ./configure --prefix=$BUILDDIR
> > > make install
> >
> > * Get FlightGear sources
> > Here you can either download the released source from the web site, or use
> > the CVS snapshot.
> > > cd $BUILDDIR/src
> > For CVS do this:
> > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login
> > > CVS passwd: guest
> > > cvs -z3 -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co
> > source
> >
> > If you want to just grab the release, then get it from the web site, and put
> > the code into src.
> >
> > * Build FlightGear
> >
> > > cd $BUILDDIR/src/FlightGear
> > > ./autogen.sh
> > > ./configure --prefix=$BUILDDIR --without-x
> > > make
> >
> > * Get the base data files (if you don't have them already)
> > again, you can just do a download from the web site, or you can use CVS.
> > For CVS do this:
> >
> > > cd $BUILDDIR (or where ever you want to put the data)
> > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login
> > CVS passwd: guest
> > cvs -z3 -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co
> > data
> >
> >

Re: [Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

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 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 !
> > -

Re: [Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

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]

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

Re: [Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

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_p

Re: [Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

./.. -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

It almost seems to have something to do with GLUT, OpenGL, gl.h, and X11.

If I try to build flightgear without setting CFLAGS and CXXFLAGS then
I get the following when building in Aircraft:

Making all in Aircraft
if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
 -I/fgfs/include  -g -O2 -D_REENTRANT -MT aircraft.o -MD -MP -MF
".deps/aircraft.Tpo" -c -o aircraft.o aircraft.cxx; \
then mv -f ".deps/aircraft.Tpo" ".deps/aircraft.Po"; else rm -f
".deps/aircraft.Tpo"; exit 1; fi
In file included from ../../src/Main/renderer.hxx:5,
 from ../../src/Main/globals.hxx:45,
 from aircraft.cxx:35:
/fgfs/include/simgear/screen/extensions.hxx:39:19: GL/gl.h: No such
file or directory
In file included from ../../src/Main/renderer.hxx:5,
 from ../../src/Main/globals.hxx:45,
 from aircraft.cxx:35:
/fgfs/include/simgear/screen/extensions.hxx:97: error: `GLenum' was not 
   declared in this scope
/fgfs/include/simgear/screen/extensions.hxx:97: error: parse error before `)' 
   token
/fgfs/include/simgear/screen/extensions.hxx:98: error: `GLclampf' was not 
   declared in this scope
/fgfs/include/simgear/screen/extensions.hxx:98: error: parse error before `,' 
   token
/fgfs/include/simgear/screen/extensions.hxx:118: error: `GLenum' was not 
   declared in this scope
/fgfs/include/simgear/screen/extensions.hxx:118: error: parse error before `,' 
   token
/fgfs/include/simgear/screen/extensions.hxx:119: error: `GLenum' was not 
   declared in this scope
/fgfs/include/simgear/screen/extensions.hxx:119: error: parse error before `,' 
   token
/fgfs/include/simgear/screen/extensions.hxx:164: error: `GLenum' was not 
   declared in this scope
/fgfs/include/simgear/screen/extensions.hxx:164: error: parse error before `)' 
   token
/fgfs/include/simgear/screen/extensions.hxx:165: error: `GLenum' was not 
   declared in this scope
/fgfs/include/simgear/screen/extensions.hxx:165: error: parse error before `)' 
   token
In file included from ../../src/Cockpit/hud.hxx:55,
 from aircraft.cxx:39:
../../src/Include/fg_typedefs.h:88: warning: use of `long double' type; its 
   size may change in a future release
../../src/Include/fg_typedefs.h:88: warning: (Long double usage is reported 
   only once for each file.
../../src/Include/fg_typedefs.h:88: warning: To disable this warning, use 
   -Wno-long-double.)
make[2]: *** [aircraft.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

And it's the same thing if I enable SDL.
Is there some way to make it use the OpenGL/GLUT framework?

You can probably tell that I hardly know what I'm doing, everything's a guess :)
Maybe if I do a fresh install of OSX it might work then. Well
FlightGear is not worth that.
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)

On Thu, 11 Nov 2004 21:04:18 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote:
> 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.  S

Re: [Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

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

[Arthur Wiebe]

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

[Arthur Wiebe]

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

[Arthur Wiebe]

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

Re: [Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

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

[Arthur Wiebe]

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] Building FlightGear on Mac OSX

[Arthur Wiebe]

I found another way to get simgear to build using GCC 3.3 and bash.

First set two environment variables:
export CFLAGS=-I/usr/X11R6/include
export CXXFLAGS=-I/usr/X11R6/include

and then run configure with the --with-x flag:
./configure --prefix=$BUILDDIR --with-x

I was able to build simgear like that without having to modify any
code. (I got it from looking at a darwinports port file)

I havn't tried building flightgear yet though.


On Wed, 10 Nov 2004 12:43:37 -0800, Adam Dershowitz
<[EMAIL PROTECTED]> wrote:
> I have made a bunch of progress, but have not yet gotten everything to work.
> So I still have some questions.
> I hope by posting this I can help others compile stuff, and also get some
> help to finish up the compile.
> Despite what the users guide says for building under OSX I have been using
> gcc 3.3.
> 
> I am sorry for the length of this email, but I have included some diffs and
> compile errors in detail.
> 
> Here are the steps that I have had to go through:
> 
>   export BUILDDIR=/Users/dersh/Programming/fgdev
> 
>   Download plib 1.8.3
> 
> Made the following changes to the files:
> 
> 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);
> 
> The last change above was because I kept getting a compile error:
> jsMacOSX.cxx: In member function `void jsJoystick::open()':
> jsMacOSX.cxx:133: error: non-lvalue in unary `&'
> 
> I don't like removing a cast without understanding the implications, but I
> did it anyway, just get it to compile.  So my first question is really a
> plib question, but it is why there is the LPVOID, and is it OK to just
> remove it?
> 
> 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];
> 
> But then building plib works fine:
> ./autogen.sh
> ./configure -prefix=$BUILDDIR
> make install
> 
> Next to build SimGear I kept getting stream related errors.  I made the
> following change to simgear/compiler.h and then I was able to get it to
> build as well:
> 
> diff compiler.h "compiler org.h"
> 82c82
> < #ifdef __GNUC__ || __APPLE__
> ---
> > #ifdef __GNUC__
> 
> It seems that even though I am using gcc, the right flag is not being set,
> so each of the test programs, that does require streams, and other standard
> IO kinds of things gave link errors.
> 
> ./autogen.sh
> ./configure -prefix=$BUILDDIR
> make install
> 
> Finally, when I try to build FlightGear I can compile everything, but the
> final like fails.
> 
> I have been doing:
> /autogen.sh
>  ./configure --prefix=$BUILDDIR --with-threads --without-x
> make install
> 
> And here is the final link warnings and errors:
> 
> g++ -DPKGLIBDIR=\"/Users/dersh/Programming/fgdev/share/FlightGear\" -g -O2
> -D_REENTRANT  -L/Users/dersh/Programming/fgdev/lib -o fgfs  bootstrap.o
> ../../src/Main/libMain.a ../../src/Aircraft/libAircraft.a
> ../../src/ATC/libATC.a ../../src/Cockpit/libCockpit.a
> ../../src/Cockpit/built_in/libBuilt_in.a ../../src/Controls/libControls.a
> ../../src/FDM/libFlight.a ../../src/FDM/Balloon/libBalloon.a
> ../../src/FDM/ExternalNet/libExternalNet.a
> ../../src/FDM/ExternalPipe/libExternalPipe.a
> ../../src/FDM/JSBSim/libJSBSim.a ../../src/FDM/YASim/libYASim.a
> ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a
> ../../src/FDM/LaRCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a
> ../../src/FDM/SP/libSPFDM.a ../../src/GUI/libGUI.a
> ../../src/Autopilot/libAutopilot.a ../../src/Input/libInput.a
> ../../src/Instrumentation/libInstrumentation.a ../../src/Model/libModel.a
> ../../src/AIModel/libAIModel.a ../../src/Network/libNetwork.a
> ../../src/Navaids/libNavaids.a ../../src/Scenery/libScenery.a
> ../../src/Scripting/libScripting.a ../../src/Sound/libSound.a
> ../../src/Airports/libAirports.a ../../src/MultiPlayer/libMultiPlayer.a
> ../../src/Replay/libReplay.a ../../src/Systems/libSystems.a
> ../../src/Time/libTime.a ../../src/Traffic/libTraffic.a
> ../../src/Environment/libEnvironment.a -lsgclouds3d -lsgroute -lsgsky

Re: [Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

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

[Arthur Wiebe]

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

[Arthur Wiebe]

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

[Flightgear-devel] Re: FlightGear on Mac OS X

[Arthur Wiebe]

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

Re: [Flightgear-devel] FG on Mac OSX

[Arthur Wiebe]

I will. (Not that I've been trying that hard lately)

The biggest problem is getting plib to compile and install. But then
again my problem was with simgear. I have some new ideas now and will
try them out. If ever I break through the ice you'll hear from me. :-)


On Mon, 8 Nov 2004 12:42:44 -0800 (PST), Jeffrey Sinsay
<[EMAIL PROTECTED]> wrote:
> 
> 
> > On Mon, 8 Nov 2004 17:42:37 +0100, Melchior FRANZ
> > <[EMAIL PROTECTED]> wrote:
> > > * Curtis L. Olson -- Monday 08 November 2004
> > 16:22:
> > > > To be fair, X-Plane does some things that are a
> > lot nicer than FG.
> > > > Also, our Mac support is woefully inadequate
> > (mostly because we have
> > > > precious few Mac developers on board.)  The
> > original poster was
> > > > referencing the Mac platform and I think his
> > comments were entirely fair.
> > >
> > Just to make myself more clear. I like FlightGear.
> > It's a great
> > simulator. I just like X-Plane better because it's
> > of better quality
> > and a more mature product. Especially on OSX :)
> >  The fact that I can't build the latest source
> > without problems I
> > don't know how to fix just adds to the reasons but
> > is not the reason.
> >
> 
> Arthur,
> 
> When you get FlightGear up and running on your Mac OSX
> system please post a good install/compile HOWTO on the
> web. I'm also a Mac OSX user and tried several months
> ago to compile the latest FG release, but ran in to
> numerous problems and never have found the time to sit
> down and try again.
> 
> I'd like to do some development work on FG with
> regards to building a good thermal model for soaring
> enthusists, but my other option besides my G4 laptop
> is the 550 Mhz PIII with Win2000 and that's a pain for
> a variety of other reasons.
> 
> Thanks
> 
> Jeff
> 
> ___
> 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