Re: [Flightgear-devel] KLN89 GPS added
On Nov 30, 2005, at 4:46 PM, David Luff wrote: Joacim Persson writes: I'm curious about the choice of language/linkage for the implementation: Why have a specific vendor model hard-coded in c++? Seems more like task for xml/nasal scripts to me. ?:-P Nothing wrong with the language (c++) but isn't it a little out of place in the fgfs /core/. That's a fair point. I used c++ because that's what I'm used to, and that's what I *know* can get the job done without running into major obstacles, whereas nasal, and adding the 'C' code function hooks for it, is an unknown quantity to me. Additionally, the c++ code could concievably be used as the basis for a standalone KLN unit simulation where nasal is not available, for instance as an X- Plane or MSFS plugin. Not on my TODO list, I hasten to add! Another way to go (in the future) could be implementing specific instrument models as plug-ins -- dynamic objects. Then the model designer can choose implementation language freely. (If for instance one is well familiar with c++ and find nasal et.al. awkward to work with.) It could also be easier to debug in that manner. (using stubs) I agree, a plugin architecture would be ideal, since then complex avionics UIs wouldn't have to add weight to the core code in terms of compilation time, compiled code size and so forth. However, a plugin architecture would have to be well thought out, and crucially, stable, to avoid plugins that by definition aren't compiled by all developers having the interface shift from beneath them. I have no experience of plugin architectures, and don't feel competent to attempt it at the moment. I'd happily alter the kln89 code to make use of one if available though. There is another issue to keep in mind for a plugin architecture which is the different platforms that FG runs on. At the moment FG probably runs on what?... maybea dozen different architectures (Hardware/OS type/Version combinations)? Each plugin would have to be built for each one? By having the code the the main part of FG then each build will include testing and fixing. However if people each develop a plugin that only works on their personal development machine it will complicate things. And many of the common architectures handle dynamic objects differently. Then would we have a whole matrix on the web site of plug in X, version Y is available for Platform Z, but will only work with FG version Q? Pick and choose, download and see what happens. If each person who does a build has to build all of the plug-ins at the same time, then they might as well just be included in the FG source code, and statically link. I am not saying that it can't be done, but there are some issue to work out. Essentially plugins would be separate mini-projects that each would have the same issues as FG itself. --Adam ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Two issues/question
On Nov 22, 2005, at 11:31 PM, Vassilii Khachaturov wrote: 1) If I fly out of an airport that is located out of the included sample scenery, then at the command line I get: Failed to open file repeated twice. I am using 0.9.8 scenery in that case, because that is all that is available. But there is no indication of what files are not opening, or what the problem is. Is there a difference This is something related to the broken exception throwing, be thankful it doesn't crash at the moment you see the message because it fetches its parts from freed memory! I'm now working on a huge patch fixing these issues all around the fg/sg/atlas/fgrun, and meanwhile you can run with --log-level=info and see what is the file it is trying to open just before the message is printed. I just tried to run it with --log-level=info, but it does not seem to be indicating anything just before the error. Here are the few lines just before each of the cases, in case it might help you. FYI, I am starting out at KLAX: Loading tile /Users/dersh/Programming/FlightGear/data/Scenery/Terrain/ w120n30/w119n33/1007339 token = OBJECT_BASE name = 1007339.btg Loading tile /Users/dersh/Programming/FlightGear/data/Scenery/Objects/ w120n30/w119n33/1007339 token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = -118.073, 33.7322 elevation = -135.99 heading = 180 token = OBJECT_SHARED name = Models/Structures/radio-medium.xml pos = -118.002, 33.7464 elevation = -151.9 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.197, 33.7494 elevation = -53.19 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.199, 33.7481 elevation = -53.19 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.197, 33.7467 elevation = -53.19 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.199, 33.7456 elevation = -53.19 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.193, 33.7425 elevation = -50.75 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.194, 33.7411 elevation = -50.75 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.197, 33.7403 elevation = -56.54 heading = 180 token = OBJECT_SHARED name = Models/fgfsdb/generic_crane_01.ac pos = -118.2, 33.7403 elevation = -57.46 heading = 180 Alert: catching up on model load queue Alert: catching up on model load queue Alert: catching up on model load queue Alert: catching up on model load queue Failed to open file Alert: catching up on model load queue Alert: catching up on model load queue Alert: catching up on model load queue Alert: catching up on model load queue Alert: catching up on model load queue Loading tile /Users/dersh/Programming/FlightGear/data/Scenery/Terrain/ w120n30/w119n34/1007371 Loading tile /Users/dersh/Programming/FlightGear/data/Scenery/Terrain/ w120n30/w118n34/1023760 token = OBJECT_BASE name = 1023760.btg Loading tile /Users/dersh/Programming/FlightGear/data/Scenery/Objects/ w120n30/w118n34/1023760 Failed to open file Refreshing timestamps for -118.375 33.9375 The one thing that I did notice from above is that there is not actually a file: Scenery/Objects/w120n30/w118n34/1023760. I have downloaded the most recent set of objects. --Adam ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Two issues/question
On Nov 23, 2005, at 12:14 PM, Martin Spott wrote: Adam Dershowitz wrote: 2) If I start with --enable-clouds3d then I just don't get any of the low level clouds to show up at all. In other words, without that feature, I get clouds at 5,000 feet, but with that flag I don't get any, but I don't see any errors either. [...] Could you try to verify if this is the same effect that I pointed at in a mail with the subject Conflicting clouds ? Thanks, I think that it probably is the same. If I start without metars, just the default: scattered at 5000, cirrus at 19500, and 2-d then it works fine. If I then use the view menu to turn on 3-d then that lower layer disappears. So I think that it is the same problem that you are seeing, and that is when 3-d clouds are enabled, they are invisible. I have not checked in the code yet, but perhaps clouds that are far away (cirrus from the ground) are not actually drawn 3-d anyway? And I can just toggle back and forth with that menu to make them appear and disappear. I just ran it with --log-level=info and this might be a clue. I see the following: initializing cloud layers texture = texture = texture = texture = texture = texture = bbcache:Initialize sucessfull RenderTexture::BeginCapture(): Texture is not initialized! bbcache:BeginCapture failed, RTT not available for 3D clouds stars = 0x11f0e0f0 stars = 0x11f0e460 SGShadowVolume:no stencil buffer, using alpha buffer Without using the higher log level I do see this error: RenderTexture::BeginCapture(): Texture is not initialized! Does this relate to 3-d clouds? I had asked about this error before, and this might be helpful to track it down. I get this same error on two different kinds of Mac hardware (Powerbook, and dual 1Ghz desktop; same software however.) --Adam ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Two issues/question
I am not sure of the status of each of these. I am using the release code of 0.9.9 on a Mac 10.4 gcc 4.0.1. 1) If I fly out of an airport that is located out of the included sample scenery, then at the command line I get: Failed to open file repeated twice. I am using 0.9.8 scenery in that case, because that is all that is available. But there is no indication of what files are not opening, or what the problem is. Is there a difference between the 0.9.8 and 0.9.9 scenery and thus this is just a bug that will go away when the new scenery build is complete? 2) If I start with --enable-clouds3d then I just don't get any of the low level clouds to show up at all. In other words, without that feature, I get clouds at 5,000 feet, but with that flag I don't get any, but I don't see any errors either. I know that a while ago 3-d clouds were broken on the Mac. Are 3d clouds now working? Does it depend on the specific video card? If they don't work, should they at least fail back to the 2d clouds that do work fine? --Adam ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 Bug
On Nov 18, 2005, at 12:45 AM, Erik Hofman wrote: Adam Dershowitz wrote: I just downloaded from CVS and built 0.9.9 and have found a bug. When it comes up the sound is muted. If I click file-sound configuration it brings up the sound dialog box with Mute Sound checked. If I uncheck it I get sound. But then I can't seem to get it to again mute. If I close the dialog box and re-open it, I can click and unclick the box, but the sound does not go away. The volume slider does work however. Once I unmute I can't get it to mute again. This sounds as if you are starting FlightGear with --disable-sound specified somewhere. The dialog seems to have a bug indeed. Erik 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 ___ 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!
On Nov 18, 2005, at 12:08 PM, Arthur Wiebe wrote: 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. ___ I downloaded and built yesterday from CVS on a Mac. I get the same error: Using Mac OS X hack for initializing C++ stdio... opening file: /Users/dersh/Programming/FlightGear/data/Navaids/ carrier_nav.dat /Users/dersh/Programming/FlightGear/data/Navaids/TACAN_freq.dat RenderTexture::BeginCapture(): Texture is not initialized! Httpd server started on port 5100 But then it continues to load and run. So I think that the error may be a red herring, and not the cause of the abort that you are seeing. --Adam ___ 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
I have the same problem as mentioned below. Has anyone figured out why, or what the work around is? I just built 0.9.9 and I get the abort below when I try to run it. I have not touched OpenAL since installing it a while back for an earlier version of FG. But my understanding is that OpenAL is now included with the Mac OS, so the version might have changed with the a system upgrade? What might be related: If I run SimGear/simgear/sound/openal_test1 then I don't get any errors, but I also don't hear anything. I get: Using Mac OS X hack for initializing C++ stdio... The cursor then goes away for a few seconds then returns, but there is total silence. If I run: SimGear/simgear/sound/openal_test2 then I get: Using Mac OS X hack for initializing C++ stdio... terminate called after throwing an instance of 'sg_exception' Abort trap Ideas? Thanks, --Adam On Nov 12, 2005, at 5:15 AM, Ima Sudonim wrote: Installing the new xcode 2.2 software on mac os 10.4.3 took about 50 minutes. (During which I did a make clean 8-) of plib, simgear and flightgear) Rebuilding plib, simgear and flightgear (latest cvs around 1pm gmt) took about one hour. Running fgfs, I get an abend: OpenAL error (AL_INVALID_VALUE): constructor (alutLoadWAVFile) terminate called after throwing an instance of 'sg_exception' Abort gcc --version powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5247) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. the old gcc version was: gcc --version powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 (Apple Computer, Inc. build 5026) Copyright (C) 2005 Free Software Foundation, Inc. Best regards, Ima ___ 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] 0.9.9 Bug
I just downloaded from CVS and built 0.9.9 and have found a bug. When it comes up the sound is muted. If I click file-sound configuration it brings up the sound dialog box with Mute Sound checked. If I uncheck it I get sound. But then I can't seem to get it to again mute. If I close the dialog box and re-open it, I can click and unclick the box, but the sound does not go away. The volume slider does work however. Once I unmute I can't get it to mute again. I am running on a Mac with OS 10.4.3 and Xcode 2.2 installed. --Adam ___ 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
I solved this problem. All I did was deleted /Library/Frameworks/OpenAL.framework because 10.4 has /System/Library/Frameworks/OpenAL.framework installed as well. Apparently gcc was finding the version of OpenAL that had been installed by the OpenAL installer that I used a while back, and not the newer one that is installed with the system. By deleting the older one it forced it to find the newer one. I also rebuilt SimGear after doing this, but I don't know if that was necessary or not. --Adam On Nov 17, 2005, at 9:45 AM, Adam Dershowitz wrote: I have the same problem as mentioned below. Has anyone figured out why, or what the work around is? I just built 0.9.9 and I get the abort below when I try to run it. I have not touched OpenAL since installing it a while back for an earlier version of FG. But my understanding is that OpenAL is now included with the Mac OS, so the version might have changed with the a system upgrade? What might be related: If I run SimGear/simgear/sound/openal_test1 then I don't get any errors, but I also don't hear anything. I get: Using Mac OS X hack for initializing C++ stdio... The cursor then goes away for a few seconds then returns, but there is total silence. If I run: SimGear/simgear/sound/openal_test2 then I get: Using Mac OS X hack for initializing C++ stdio... terminate called after throwing an instance of 'sg_exception' Abort trap Ideas? Thanks, --Adam On Nov 12, 2005, at 5:15 AM, Ima Sudonim wrote: Installing the new xcode 2.2 software on mac os 10.4.3 took about 50 minutes. (During which I did a make clean 8-) of plib, simgear and flightgear) Rebuilding plib, simgear and flightgear (latest cvs around 1pm gmt) took about one hour. Running fgfs, I get an abend: OpenAL error (AL_INVALID_VALUE): constructor (alutLoadWAVFile) terminate called after throwing an instance of 'sg_exception' Abort gcc --version powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5247) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. the old gcc version was: gcc --version powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 (Apple Computer, Inc. build 5026) Copyright (C) 2005 Free Software Foundation, Inc. Best regards, Ima ___ 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 mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] XCode project files
--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
Re: [Flightgear-devel] How does the weather work in FlightGear?
On Oct 10, 2005, at 10:26 AM, Ampere K. Hardraade wrote:On October 10, 2005 03:37 am, Erik Hofman wrote: Buchanan, Stuart wrote: FlightGear can fetch the current weather at yourstarting airport, or you can set the wind, cloudlayers etc manually. I don't know if the weatherconditions are global, or change as you fly todifferent locations. It interprets the data from the nearest METAR station. The data isfetched from noaa.gov.Erik In my opinion, it would be better if data from multiple nearby METAR stations is used instead of fetching data from only one station. I often fly with real-weather-fetch enabled, and the plane gets a huge jolt whenever the weather is updated. The change in the visual aspects is also too sudden. Using data from multiple METAR stations could avoid the above problems and allow us to have a smooth transistion in weather.AmpereThis is not as obvious as it would first seem. Some weather phenomena have very sharp transitions and some are gradual. So I don't think that "interpolating weather" is a trivial thing to do. For example a cold front is often a very well defined line with rain right along the front. In that case the weather right nearby is the best indicator and a METAR from 5 miles away could give a completely different story. Airmass thunderstorms are another example where very local weather is what matters. To make maters worse the METAR will just have temperature and wind, so you would have to look at a few different locations and times to figure out that a front has passed. And the local geography (mountains, lake effects, shore lines) can also be a significant issue.I am not saying that it could not be done, just that it would take some real thought and real understanding of weather phenomena for it to apply in the general case rather than just in a few specific case and make things worse other times. --Adam ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] configure error
This is a known problem with building FlightGear on a Mac. For some reason autogen for FG does not copy them, while it works fine for SimGear. I have not been able to figure out why it happens, or what is 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.sh Automake should do the next two steps, but for some reason does not for FlightGear (but it does for SimGear, which is odd) ln -s /usr/share/automake-1.6/config.guess config.guess ln -s /usr/share/automake-1.6/config.sub config.sub ./configure --prefix=$BUILDDIR --without-x make Does anyone know if my Mac build instructions were ever included in any documentation anywhere? Best I can tell, the only Mac build instructions are very old, out of date, and don't work at all. Instead they just lead newbies off in a completely wrong direction. --Adam On 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 mailto:[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] mailto:[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 mailto:Flightgear- [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Arthur/ - http://sourceforge.net/users/artooro/ http://sourceforge.net/users/artooro/ - http://artooro.blogspot.com http://artooro.blogspot.com -- Arthur/ - http://sourceforge.net/users/artooro/ http://sourceforge.net/users/artooro/ - http://artooro.blogspot.com http://artooro.blogspot.com ATT25937233.txt ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] carb-heat
According to the C-172P POH I have here:
If conditions require the the continued use of carburetor heat in cruise
flight, use the minimum amount of heat necessary to prevent ice from forming
and lean the mixture for smoothest engine operation.
So, no, not too pedantic at all.
-- Adam
From: Jim Campbell [EMAIL PROTECTED]
Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org
Date: Mon, 20 Jun 2005 10:59:45 +0100
To: flightgear-devel@flightgear.org
Subject: [Flightgear-devel] carb-heat
Hi,
On the Cessna 172/150 range of aircraft the carb-heat control is a
progressive
knob as for mixture. The operators recommendation is indeed that only
FULL or
off should be used and it is represented as bool in flight gear but
is this a correct
interpretation. If the actual aircraft panel is a variable control
should the representation
be variable and up to the pilot to use in the recommended fashion.
Anyone any opinions
on this point (maybe I am just being too pendantic!!)?
cheers
Jim
FGControls::set_carb_heat( int engine, bool val )
{
if ( engine == ALL_ENGINES ) {
for ( int i = 0; i MAX_ENGINES; i++ ) {
carb_heat[i] = val;
}
} else {
if ( (engine = 0) (engine MAX_ENGINES) ) {
carb_heat[engine] = val;
}
}
}
___
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] splash screen distortion
Yes, I do get the same thing. MacOS 10.3 Fg 0.9.8 -- Adam From: Dave Culp [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Mon, 23 May 2005 00:06:08 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: [Flightgear-devel] splash screen distortion During sim startup, about 2 or 3 seconds before the world appears, the splash image is distorted, most often stretched vertically, sometimes split in two vertically. It's been doing this for a long time, maybe a year or more, but I've been ignoring it until now. Anyone else getting this? Mandrake 10.1 nVidia MX440 with latest driver cvs plib, SimGear, FlightGear glut, openal Dave ___ 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] Scratch Build Problem
Yup. For some reason there is something odd, that I was never able to figure out for Mac builds. I don't know why, but automake on the mac, does not do the required links for building flightgear itself, but it does work fine for SimGear and plib...I don't get it. But here is the relevant part to solve the problem from my build instructions: * Build FlightGear cd $BUILDDIR/src/source ./autogen.sh Automake should do the next two steps, but for some reason does not for FlightGear (but it does for SimGear, which is odd) ln -s /usr/share/automake-1.6/config.guess config.guess ln -s /usr/share/automake-1.6/config.sub config.sub ./configure --prefix=$BUILDDIR --without-x make I have not tried a recent build from CVS, so I am curious if it works OK on the mac, so please let me know. -- Adam From: Jonathan Polley [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Wed, 18 May 2005 23:27:23 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: [Flightgear-devel] Scratch Build Problem I was having a problem getting FlightGear to link, so I decided to do a complete uninstall and delete of the development directories. After a clean fetch from CVS, I was able to rebuild SimGear, but FlightGear won't even configure. I get the following error: configure: error: cannot run /bin/sh ./config.sub and config.sub was not generated by ./autogen.sh. Any ideas as to what needs to be done? Thanks, Jonathan Polley ___ 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] Re: Speed of CVS version and flying in theHimalayas
I hope you were using Oxygen (for you and the engine!) -- Adam From: Paul Furber [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Tue, 03 May 2005 23:59:15 +0200 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: Re: [Flightgear-devel] Re: Speed of CVS version and flying in theHimalayas On Tue, 2005-05-03 at 14:46 -0400, Ampere K. Hardraade wrote: On May 3, 2005 01:52 pm, Paul Furber wrote: Thanks - I did have it the right way around when running it - just typed it in wrong in the previous e-mail. I've just downloaded the e080n20 tileset and there now seems to be a large peak of ~29 000ft on the China/Nepal border :] Some screenshots will be nice. Ask and ye shall receive: Flying WNW towards the summit in the Cessna. The SouthEast ridge slopes away to the right and in the saddle on the far right is the top of the Lhotse face. http://www.paulfurberconsulting.com/images/fgfs-everest-1.jpg An external view: http://www.paulfurberconsulting.com/images/fgfs-everest-2.jpg -- Paul Furber [EMAIL PROTECTED] ex tenebris lux, ex fenestris tux -- ___ 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] Re: Repeated image capture
OK, I got things working, but I have another question. First off, to get things to work, I had to rebuild SimGear --with-jpeg-factory and then reconfigure and rebuild FlightGear. The configure process actually checked for jpeg, so when it is not available it gives an error even though the help says that it works. So I just wrote a shell script that uses curl to grab images periodically. Not elegant or efficient, but it does work. But, once I got that working, it seems that the jpegs that are returned are just a small part of the screen. It does a crop for a lower corner. If I resize the screen to just the right size then I can get the returned images to cover the full window. Is there a way to get --jpg-httpd to return the full window? It seems like that should be the behavior, and dragging to resize the window should just resize the resultant jpg. Any ideas? Thanks, -- Adam From: Adam Dershowitz [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Wed, 27 Apr 2005 15:48:58 -0700 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: Re: [Flightgear-devel] Re: Repeated image capture Nope, I just missed it in my email (as I missed the n in Unknown as well), not in my actual test. But, good thought. It does seem strange to me that the option shows in the verbose help, but gives an unknown option error when I try it. By the way, I am using version 0.9.8 right now. Thanks, -- Adam From: Melchior FRANZ [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Thu, 28 Apr 2005 00:39:04 +0200 To: flightgear-devel@flightgear.org Subject: [Flightgear-devel] Re: Repeated image capture * Adam Dershowitz -- Thursday 28 April 2005 00:31: I tried to run with --jpg-http=5432 but then I get an error Unkown option. $ fgfs --verbose --help|grep jpg --jpg-httpd=port Enable screen shot http server on the specified ^ You missed the 'd' (for daemon). m. ___ 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 mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Repeated image capture
Is there any way to do a repeated image capture in FG? I have thought about a few things, but none seems to work how I want. I would like to build a movie, and would start out by just saving snapshots, then, after I am done, building up the movie. I thought that I might be able to write a simple script that will telnet to FG, then issue the run screen-capture command repeatedly. The problem is that when I do that, it works the first time, but it brings up the dialog box that says where the image was saved, and requires me to click OK. If I just repeat the command, without hitting OK, then the next image has this dialog box in the middle. I also figured that I could try to write a simple script to capture stuff from an HTTP connection. I tried to run with --jpg-http=5432 but then I get an error Unkown option. I think this might be because I did not do my initial SimGear build with --with-jpeg-factory. But I figured I would try to confirm this by asking, and that it should work OK before I do a rebuild? There was some discussion on the list a little while back that this feature was not working correctly at the time. Will that likely do the job? How much of a performance hit will there be to do the jpeg compression? I am running on a Mac, and I know that there are a few shareware applications that will do screen captures, but it seems like it should be able to be done without purchasing software. Any other suggestions? Thanks, -- Adam ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Repeated image capture
Nope, I just missed it in my email (as I missed the n in Unknown as well), not in my actual test. But, good thought. It does seem strange to me that the option shows in the verbose help, but gives an unknown option error when I try it. By the way, I am using version 0.9.8 right now. Thanks, -- Adam From: Melchior FRANZ [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Thu, 28 Apr 2005 00:39:04 +0200 To: flightgear-devel@flightgear.org Subject: [Flightgear-devel] Re: Repeated image capture * Adam Dershowitz -- Thursday 28 April 2005 00:31: I tried to run with --jpg-http=5432 but then I get an error Unkown option. $ fgfs --verbose --help|grep jpg --jpg-httpd=port Enable screen shot http server on the specified ^ You missed the 'd' (for daemon). m. ___ 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] Another fgfs enabled rating!
Dave, Congrats! The instrument rating is a particularly difficult rating, but is also a very useful rating to have. Martin: Yes, in the US it is often done in single engine airplanes. There is a lot of single engine IFR flying here, so the rating is very useful on its own, rather than as a step to other ratings. It really increases the utility of a airplane greatly when a few clouds don't ground you. --Adam CFI,II, MEI,II -Original Message- From: Martin Spott To: flightgear-devel@flightgear.org Sent: 4/22/2005 2:00 AM Subject: Re: [Flightgear-devel] Another fgfs enabled rating! Dave Perry wrote: I passed my instrument rating oral and practical (check ride) this afternoon. Five hours including the oral and ride. Wow, this is great. Hmmm, I feel I'm getting envious ;-) [...] The examiner said I did an outstanding job given the conditions. I flelt like I was always flying back to where I wanted to be with the many significant up and down drafts. the Piper Comanche (PA24-250) performed well. Oh, you did your instrumental on a single engine aircraft ? In our country IFR (training and rating) is always done on multi-engine (to my knowledge) because it's meant as a step for the ATPL. This makes it almost unaffordable for individuals Well, I've still a long way to go before I face decisions like this. Yesterday I had my first solo traffic circuits on foreign airfields (two of them), still a nice experience :-) Congtatulations, 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 ___ 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
There is: -- Adam From: Felix [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Thu, 3 Mar 2005 15:45:59 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: Re: [Flightgear-devel] Compiling Flightgear 0.9 from CVS on Mac OS X I wish there was a document that would go over the entire build for Mac OS X. I forgot to build OpenAL for SimGear and i'm having difficulty. OpenAL has two a Macosx directory in the CVS Repository, and a Linux one. The mac os x one has an xcode project that doesn't build in xcode, and the linux one won't build either and fails with the following: cd jlib make all make[1]: Nothing to be done for `all'. cd src make all gcc -I../../include -I../include -I../audioconvert -Iarch -I. -g -O2 -fPIC -Wshadow -Wall -W -Wbad-function-cast -Wcast-qual -Wcast-align -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wimplicit-function-declaration -Waggregate-return -Winline -Wpointer-arith -fno-common -Wredundant-decls -c al_ext.c -o al_ext.o al_ext.c: In function `alGetEnumValue': al_ext.c:693: error: `AL_STREAMING' undeclared (first use in this function) al_ext.c:693: error: (Each undeclared identifier is reported only once al_ext.c:693: error: for each function it appears in.) al_ext.c:737: error: `AL_BYTE_LOKI' undeclared (first use in this function) al_ext.c:865: error: `AL_DISTANCE_SCALE' undeclared (first use in this function) al_ext.c:873: error: `AL_ENV_ROOM_IASIG' undeclared (first use in this function) al_ext.c:877: error: `AL_ENV_ROOM_HIGH_FREQUENCY_IASIG' undeclared (first use in this function) al_ext.c:881: error: `AL_ENV_ROOM_ROLLOFF_FACTOR_IASIG' undeclared (first use in this function) al_ext.c:885: error: `AL_ENV_DECAY_TIME_IASIG' undeclared (first use in this function) al_ext.c:889: error: `AL_ENV_DECAY_HIGH_FREQUENCY_RATIO_IASIG' undeclared (first use in this function) al_ext.c:893: error: `AL_ENV_REFLECTIONS_IASIG' undeclared (first use in this function) al_ext.c:897: error: `AL_ENV_REFLECTIONS_DELAY_IASIG' undeclared (first use in this function) al_ext.c:901: error: `AL_ENV_REVERB_IASIG' undeclared (first use in this function) al_ext.c:905: error: `AL_ENV_REVERB_DELAY_IASIG' undeclared (first use in this function) al_ext.c:909: error: `AL_ENV_DIFFUSION_IASIG' undeclared (first use in this function) al_ext.c:913: error: `AL_ENV_DENSITY_IASIG' undeclared (first use in this function) al_ext.c:917: error: `AL_ENV_HIGH_FREQUENCY_REFERENCE_IASIG' undeclared (first use in this function) make[1]: *** [al_ext.o] Error 1 make: *** [all] Error 2 I Know that i can just download the Mac OS X binary for FlightGear, but i'd much rather be able to build it from scratch so that i can play around with the code. Any ideas about my latest problem? Thanks again! Felix On Thu, 03 Mar 2005 11:52:15 -0600, Jonathan Polley [EMAIL PROTECTED] wrote: I am using MacOS X 10.3 and don't remember having to upgrade the automake tools, but I have updated to the most recent Xcode release. On Thursday, March 03, 2005, at 08:38AM, Arthur Wiebe [EMAIL PROTECTED] wrote: 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=26350group_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 -- Arthur/ - 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 Of COURSE they can do that. They're engineers! ___ 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
Re: [Flightgear-devel] Compiling Flightgear 0.9 from CVS on Mac OS X
The mac build instructions should be included somewhere. If not here are the steps that you are having problems with: * Build FlightGear cd $BUILDDIR/src/source ./autogen.sh Automake should do the next two steps, but for some reason does not for FlightGear (but it does for SimGear, which is odd) ln -s /usr/share/automake-1.6/config.guess config.guess ln -s /usr/share/automake-1.6/config.sub config.sub ./configure --prefix=$BUILDDIR --without-x make You should only have to do this the first time that you build. -- Adam From: Felix [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Wed, 2 Mar 2005 22:56:42 -0500 To: flightgear-devel@flightgear.org Subject: [Flightgear-devel] Compiling Flightgear 0.9 from CVS on Mac OS X Hi, I am trying to compile FlightGear 09 on a Mac OS X. I got plib, and SimGear installed fine. But FlightGear won't perform the autogen.sh correctly. For some reason it doesn't generate the config.sub files necessary for ./configure. When i run ./configure i get: configure: error: cannot run /bin/sh ./config.sub and the reason for that is that config.sub isn't there. Autogen.sh creates links for config.sub and others for SimGear, but not for FlightGear. I read some posts on this list from other people who had the same problem, but no one had a solution. Anyone have any ideas what i can try? Thank you, Felix ___ 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] Mac os x simgear build break with RenderTexture.cpp
If you have any luck building Atlas on a Mac, please let me know. I have had problems with the automake stuff, and I have not yet managed to get it to compile. -- Adam From: James Turner [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Tue, 1 Feb 2005 15:23:50 + To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: Re: [Flightgear-devel] Mac os x simgear build break with RenderTexture.cpp On 1 Feb 2005, at 15:11, Erik Hofman wrote: It is not yet used. I've put the code in CVS in different stages to get developers the chance to get things working without being overwhelmed with changes. At least Atlas can use this code to render the maps (accelerated) in the background though. Ok. I note that Manuel's excellent looking terrain code is using impostors, and hence will need this too, but also that GL 1.5 has finally ratified the render buffer object extension, so coding up the pbuffer stuff will be a temporary measure, with a bit of luck - render buffers are platform independent. Assuming I was to add support, is there a simple test-case? Or do I need to build Atlas? HH James -- They are laughing with me, not at me. ___ 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] Mac os x simgear build break with RenderTexture.cpp
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 flightgear-devel@flightgear.org Date: Mon, 31 Jan 2005 18:46:07 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org 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 -- Arthur/ - 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
Re: [Flightgear-devel] Atlas release candidate
I have never tried to build Atlas before, but just tried with this release. I am working on a Mac and ./configure gives me the following errors: checking for pthread_exit in -lpthread... yes checking for glNewList in -lGLcore... no checking for glNewList in -lGL... yes checking for gluLookAt in -lGLU... yes checking for glutGetModifiers in -lglut... no checking for glutGameModeString in -lglut... no Unable to find the necessary OpenGL or GLUT libraries. See config.log for automated test details and results ... In order to build flightgear, a little while ago, it was necessary to make a few changes to the source code to get it to properly find GLUT stuff. But these changes are now all incorporated into FG. These locations are now all captured in simgear/compiler.h. In the time that I have been working with the code, no changes were required to the config stuff, only some of the paths in the source itself, now in compiler.h. The truth is that I have not done much with automake, so I am not really sure how to go about fixing this. But clearly something is different in how Atlas checks for GLUT versus how Simgear and FG do it, since they succeed just fine in finding and using that stuff. If you can point me in the right direction I can try to work with it some more. Atlas looks very useful. Thanks, -- Adam From: David Luff [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Fri, 28 Jan 2005 13:16:28 + To: [EMAIL PROTECTED] Cc: flightgear-devel@flightgear.org Subject: [Flightgear-devel] Atlas release candidate Hi all, I've put a release candidate of Atlas-0.3 up at: http://www.nottingham.ac.uk/~eazdluf/Atlas-0.3.0-rc1.tar.gz If a few folk could take the time to download this and try it out that would be great. Changes in the last year or so: * Now reads FG-0.9.8 airport and navaid formats * Atlas now displays ILS localisers * Map has an off-screen rendering option (--headless) to avoid image corruption due to overlaid windows and possibly allow maps greater than screen resolution depending on graphics hardware and drivers [X-Windows with fairly modern GLX only at present] * Map supports multiple scenery paths via FG_SCENERY or --fg-scenery= (only Map at present, not MapPS). * Atlas has --airport=ICAO startup option. * Bug fixes. Note that Atlas/Map is written by Per Liedman and others, not myself, but Per is unable to maintain it at the moment. Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ 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 0.9.8, Mac OS X build
Rather than trying to get into a religious discussion with you, which clearly would be pointless, I will try to explain a different issue. This simply does not relate to FlightGear! Yes, we each could build releases with our own personal, religious, ethnic, or political message, but that is not going to help with FG, but instead is going to get a bunch of people arguing, as has already been demonstrated. (Are you going to download the Catholic FlightGear, or the Jewish One, or the Democratic, or anti-gay version...?). It will get very silly very quickly. There are plenty of places to argue about religion, if you choose. The problem is that you have chosen to use the work of others as a platform for your personal beliefs. While you can do that under the license, it surely is not the intent of the other people who are working on this. Many of us find it extremely offensive to have the appearance that our work is supporting your message, which we disagree with. So, no, it does not satisfy the issue. Would you feel uncomfortable if there were a version of FG that was explicitly anti-Jesus? Would you be willing to work on it? I don't mean this as a threat, but instead to help you understand what some other people are feeling. So I am explicitly asking you to please consider removing your personal message from the package. -- Adam From: Arthur Wiebe [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Thu, 20 Jan 2005 14:24:38 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: Re: [Flightgear-devel] FlightGear 0.9.8, Mac OS X build 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 -- Arthur/ - 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
Re: [Flightgear-devel] Announce v0.9.8
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 flightgear-devel@flightgear.org Date: Wed, 19 Jan 2005 16:43:53 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org 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 -- Arthur/ - 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
Re: [Flightgear-devel] Announce v0.9.8
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 flightgear-devel@flightgear.org Date: Wed, 19 Jan 2005 17:56:52 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org 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 flightgear-devel@flightgear.org Date: Wed, 19 Jan 2005 16:43:53 -0500 To: FlightGear developers discussions flightgear-devel@flightgear.org 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 -- Arthur/ - 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 -- Arthur/ - 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
Re: [Flightgear-devel] Antonov AN-225.
Does anyone know if there is something similar in JSBSim? It seems that the spoilers there are only symmetric, so are useful for landing, but not for in flight use? -- Adam From: Andy Ross [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Mon, 17 Jan 2005 16:40:52 -0800 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: Re: [Flightgear-devel] Antonov AN-225. Curtis L. Olson wrote: Bear in mind that one thing that is commonly done on many aircraft is to pop up a spoiler on the wing that should drop. This can be a lot more effective than just deflecting airflow with the aileron. To my knowledge, YAsim doesn't model this directly [...] Actually, it does. There is a SPOILER control that you can map on wing/hstab/vstab objects. I don't think anything has used it yet for roll control, but it ought to work. Remember to set split=1 to make it asymmetric. Andy ___ 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] Antonov AN-225.
From: Jon Berndt [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Mon, 17 Jan 2005 22:00:28 -0600 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: RE: [Flightgear-devel] Antonov AN-225. Does anyone know if there is something similar in JSBSim? It seems that the spoilers there are only symmetric, so are useful for landing, but not for in flight use? -- Adam It hasn't been done, yet - I was just discussing this offline with someone. Let me say that, yes, it certainly CAN be done, without question. At one time years ago I modeled certain aerodynamic aspects of a military aircraft and great pains were taken to model similar things, and other much smaller effects. The effect cannot be modeled without some thought, though. Remember that JSBSim models aerodynamic forces and moments using aerodynamic coefficients and stability derivatives. By calculations, empirical data, flight test data, etc. one can usually determine the total (symmetric) effects of spoilers which will generally be: 1) effect on lift 2) effect on drag 3) effect on pitching moment If the spoilers are deployed asymmetrically, the effects are wider: 1) effect on lift 2) effect on drag 3) effect on pitching moment 4) roll 5) yaw 6) side force ... all six axes ... If we can determine the symmetric case, we can figure out the asymmetric case. Jon That sounds to me like the difficulty is in choosing (finding?) the coefficients, rather than in the coding of JSBSim? I don't mean to minimize the difficulty of finding all of those coefficients, but in some sense that is really a different problem than can JSBSim do it? Lot's of aircraft use spoilers for some part of roll control, so it seems to me that would be an important addition to JSBSim. Typically the spoilers will only deploy above some yoke position threshold (maybe actually a roll rate?), and then they can, of course, only deploy up, so only one is involved at a time. This all does make it somewhat ugly. But often, for modeling, finding the correct parameters is the hardest part, once the code can handle what is needed. So, please add me to the requesters, and add me to the offline discussion. Thanks, --Adam ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: Aircraft/Pilot's manuals
For GA aircraft (light aircraft) the POH is pretty much all there is, other than maintenance manuals. The POH does not contain complete system information. It contains enough for a pilot to understand the OPERATION of the systems, so there are often some simplifications and approximations. So this could lead to some issues for detailed modeling. The maintenance manuals contain more details about systems, but they tend to be harder to get, and then contain lots of other stuff that is not relevant, or that useful for modeling. To complicate things, I believe that airlines are often involved in the specific manuals that are used on their airplanes. In other words I think that if you got into the cockpit of a 737-800, the included manuals would depend on what AIRLINE owns the airplane. They would have worked with Boeing to generate them. I am getting into more guesswork, then knowledge, but I would not be surprised if the Operations Manual relates to people outside of the cockpit (maintenance, dispatch etc.) rather than the people inside the cockpit (Pilot's Handbook). Finally, I would say that your best starting point will generally be the POH, but modeling an airplane is complex, and much of the data is considered proprietary and is not available, even to owners and operators. It is generated during certification and then held close. -- Adam From: Paul Surgeon [EMAIL PROTECTED] Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org Date: Wed, 5 Jan 2005 21:23:33 +0200 To: FlightGear developers discussions flightgear-devel@flightgear.org Subject: [Flightgear-devel] OT: Aircraft/Pilot's manuals I'm not a pilot so could someone more informed than myself please tell me which is the best type of manual to get if one wants to model an aircraft including the avionics? Does a POH/PIM contain the most useful info? More importantly does it describe aircraft systems as well as procedures? What is the difference between an Operations Manual and a Pilot's Handbook? (Boeing) What is a Flight Study Guide? (The A340 one is 4 volumes) What is a Flight Manual? (I know it's not a Operations Manual) Thanks Paul ___ 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] Re: Flightgear-devel Digest, Vol 20, Issue 45
From: Curtis L. Olson [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Mon, 20 Dec 2004 06:08:51 -0600 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: Flightgear-devel Digest, Vol 20, Issue 45 Jon Stockill wrote: Thomas Förster wrote: I also thought about this as an option for a GUI. The main advantage would be that this approach ensures there's no GUI code in FG and there is a well designed API/Protocol to it. Writing alternative GUI's should be easy using that API/Protocol. Having the GUI seperated also makes it easy to distribute the apps across machines, i.e. having a simulator with an instructors workplace (changing weather, fail engines...) With the added advantage of not bloating the simulator - gets my vote. For what it's worth, I think that some sort of minimal built in gui for FG is still a good idea. FG already provides a lot of support for developing an external gui (i.e. for an operator/instructor station.) I have done exactly this for the ATC flight sim single engine trainer and it works quite well. The only issue is that for single PC, home users who aren't immensely computer savey, starting up multiple apps concurrently can be a bit tricky ... especially in a multiplatform / portable context. 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 But cross platform support gets more difficult. This is somewhat demonstrated by the issues that someone is having right now getting fgrun to compile and build. By keeping a single application there is a bunch of support, and a bunch of drive to keep the code base working across platforms. If the code splits into a bunch of different applications then people are needed to build/test/support each separate app. on each platform. In theory that should not be that hard, but in reality, I believe, no one has yet built fgrun for the Mac... --Adam ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Flightgear-devel Digest, Vol 20, Issue 45
I realize that. I just meant that the more the source code forks into different applications the harder it will be to keep it all working across platforms. Each person who is working on their own particular app. Will make sure that it works on their own platform. While if there is one FlightGear app. Then there is a joint effort, with each change in source, to get it to work across many platforms. -- Adam From: Martin Spott [EMAIL PROTECTED] Organization: home Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Newsgroups: list.flightgear-devel Date: Mon, 20 Dec 2004 20:34:15 + (UTC) To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: Flightgear-devel Digest, Vol 20, Issue 45 Adam Dershowitz wrote: But cross platform support gets more difficult. This is somewhat demonstrated by the issues that someone is having right now getting fgrun to compile and build. Well, David Luff has proven that cross-platform-portability is not a miracle, his TaxiDraw compiles at least on Windows and five different Unices just with some small Makefile changes allthough he didn't tell us how much effort he had to spend in order to achieve this portability ;-) Cheers, 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] control surface normalization
I disagree. It is easy to say what is natural, but hard to show it. After someone has been flying for a while it sure feels natural. But when I have a new student I find that very often they over control the aircraft. I can get them to quite down by convincing them to just use pressure. Maybe we are just arguing semantics, but I think that it is learned, not natural. -- Adam From: Gordan Sikic [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Fri, 17 Dec 2004 09:22:17 +0100 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] control surface normalization Hi, Pilots are taught to think in terms of pressure on stick not displacement. That is part of the reason that the F-16 is built the way it is. Thats OK, I agree, with one small change: pilots are not *taught* to think in terms in terms of pressure on stick. It is the natural way of sensing the aircraft. cheers, Gordan ___ 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] FlightGear Mac OS X Application Bundle Available
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! :) -- Arthur/ ___ 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 -- Arthur/ - 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
Re: [Flightgear-devel] control surface normalization
Pilots are taught to think in terms of pressure on stick not displacement. That is part of the reason that the F-16 is built the way it is. -- Adam Dershowitz, Ph.D., CFI, MEI From: Gordan Sikic [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 16 Dec 2004 23:08:30 +0100 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] control surface normalization Hi Jon, I see you are really mad :) Look here at the X-15 data and FCS diagram: http://jsbsim.sourceforge.net/X-15Aero.html The USAF F-16 (Block 40) FCS diagram is the same way: stick force is the input. Same with Space Shuttle control Law diagrams. The JSBSim X-15 model simulates the X-15 control laws as shown in the link above. We take the -1 to +1 joystick input from FlightGear and turn it into a stick force, mapping to the force range described in Etkin's book as a sort of standard. These are 3 particular examples only. (about F16) AFAIK, it has nonmoving joystick, and force transducers, and it is normal for that plane to ise output from the transduced as a input. (about X15) AFAIK, it had 2 completely different (unconnected?) sticks, one for lower speeds (usual stick), and the other one (joystick actually) used for control in higer speeds regimes. Does it apply for both sticks? As I mentioned, these are 3 particular examples only, not a general rule . cheers, :) Gordan ___ 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: [Simgear-cvslogs]
Perhaps this is why it is OK with OSX?
-- Adam
From: Curtis L. Olson [EMAIL PROTECTED]
Reply-To: FlightGear developers discussions [EMAIL PROTECTED]
Date: Thu, 02 Dec 2004 09:02:16 -0600
To: FlightGear developers discussions [EMAIL PROTECTED], J.
Couch [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] Re: [Simgear-cvslogs]
Hi Martin,
Ok, this sounds reasonable. I assume this means that the isnan()
problems are fixed in newer versions of FreeBSD?
Thanks,
Curt.
Martin Spott wrote:
Hello Curt,
could you please revert this change and remove the whole FreeBSD
clause - it just makes life harder on the cuurrent FreeBSD RELEASE - or
change it. See below.
Curtis L. Olson wrote:
Update of /var/cvs/SimGear-0.3/source/simgear/sound
In directory baron:/tmp/cvs-serv27687/sound
Modified Files:
soundmgr_openal.cxx
Log Message:
I don't understand why FreeBSD doesn't see isnan() after including math.h
but it doesn't. Trying the apple approach to fixing isnan results in an
infinite loop (making me wonder what happens on OSX?) This is an
alternative
approach to checking isnan() on freebsd ...
Index: soundmgr_openal.cxx
===
RCS file: /var/cvs/SimGear-0.3/source/simgear/sound/soundmgr_openal.cxx,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -r1.7 -r1.8
*** soundmgr_openal.cxx 19 Nov 2004 21:44:17 - 1.7
--- soundmgr_openal.cxx 21 Nov 2004 03:13:54 - 1.8
[...]
***
*** 47,50
--- 47,54
#endif
+ #if defined (__FreeBSD__)
+ inline int isnan(double r) { return !(r 0 || r 0); }
+ #endif
+
#include STL_IOSTREAM
An alternative to keep compatibility with older FreeBSD releases might
be to place such a clause:
#if defined (__FreeBSD__)
extern C {
#if __FreeBSD_version 50
inline int isnan(double r) { return !(r = 0 || r = 0); }
#endif
}
#endif
Thanks alot,
Martin.
--
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] Build Problem Under MacOS X 10.3
Yes, Ima caught that mistake and emailed me, but I guess that the fix was not put into CVS. Curt, can you fix this in CVS? As you can see below: In compiler.h For the __APPLE__ case, it has: #define SG_GLUT_H OpenGL/glut.h When it should be: #define SG_GLUT_H GLUT/glut.h I still don't understand why I was able to get it to build this way, so I did not catch it, but that is just an academic question at this point. -- Adam From: Jonathan Polley [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Tue, 30 Nov 2004 20:02:55 -0600 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: [Flightgear-devel] Build Problem Under MacOS X 10.3 I tried building with the latest MacOS changes from CVS and found one problem. When compiler.h gets generated, the symbol SG_GLUT_H gets defined to be OpenGL/glut.h when it needs to be defined as GLUT/glut.h. It is a part of the GLUT framework and not the OpenGL framework. Thanks, Jonathan Polley ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Not yet. Seems that there are some patches necessary. They are just ifdef stuff, but it will require a few changes to CVS, to make it easy to build. I think that it is a better idea to get those changes into CVS, then to put all the patches into the build instructions. I will try to get to it, but, like a lot of folks here, I am pretty busy. If anyone else gets to it, then we can finish up the docs. -- Adam From: Martin Spott [EMAIL PROTECTED] Organization: home Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Newsgroups: list.flightgear-devel Date: Mon, 15 Nov 2004 11:23:21 + (UTC) To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X Adam Dershowitz wrote: I took a whack at drafting up a new set of Mac build instructions for the users guide. I would appreciate it if someone else could try to run through this step by step just to confirm that I did not miss anything (another set of eyes and a different computer is pretty useful for checking.). Well, do Mac users consider this as ready for inclusion into the manual ? To be honest, I'd be happy if Adam would post a revides version which includes the feedback what we have seen on this list and probably off-list. Thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
OK, I took a whack at drafting up a new set of Mac build instructions for the users guide. I would appreciate it if someone else could try to run through this step by step just to confirm that I did not miss anything (another set of eyes and a different computer is pretty useful for checking.). Arthur, since you are trying a bunch, perhaps you can start completely from scratch and just follow through these instructions step by step. It might help you and it might help get them checked. Anyway, I hope this is helpful. If anyone has any other edits or suggestions I would be happy to hear them or just pass them directly to Martin. --Adam And here are is the new procedure: How to build FlightGear v0.9.6 on Mac OS X. These steps worked fine for me, but I don't know if other OS versions etc. might also work: Mac OS 10.3.6 XCode 1.5 By default this included gcc 3.3, autotmake 1.6.3, autoconf 2.53, so nothing else is required. * Setup the build environment: Create the directory to build into, and one for the source. For example: mkdir FlightGear mkdir FlightGear/src then I like to just create an environment variable to this: export BUILDDIR=/where/ever/you/created/FlightGear * Download PLIB I first tried to use plib 1.8.3 but that will not compile properly on a Mac without a few changes. But, as of this writing, the CVS version will. You can either use CVS, or grab the snapshot from here: http://plib.sourceforge.net/dist/current.tgz If you open the above link it should automatically unpack to create a folder called plib. Drag (or copy) that folder into /where/ever/you/created/FlightGear/src * Build PLIB cd $BUILDDIR/src/plib ./autogen.sh ./configure --prefix=$BUILDDIR make install * Get SimGear sources cd $BUILDDIR/src cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.3 login # Enter guest for password cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.3 -z3 co SimGear * Build SimGear cd $BUILDDIR/src/SimGear ./autogen.sh ./configure --prefix=$BUILDDIR make install * Get FlightGear sources Here you can either download the released source from the web site, or use the CVS snapshot. cd $BUILDDIR/src For CVS do this: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login CVS passwd: guest cvs -z3 -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co source If you want to just grab the release, then get it from the web site, and put the code into src. * Build FlightGear cd $BUILDDIR/src/FlightGear ./autogen.sh ./configure --prefix=$BUILDDIR --without-x make * Get the base data files (if you don't have them already) again, you can just do a download from the web site, or you can use CVS. For CVS do this: cd $BUILDDIR (or where ever you want to put the data) cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login CVS passwd: guest cvs -z3 -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co data * You are now ready to run FlightGear. There are a few different ways to do it. If you just do: cd $BUILDDIR src/FlightGear/src/Main/fgfs --fg-root=/path/to/data It should run. I believe that it will also try to search in $BUILDDIR/fgfsbase for data. Finally it will search for a file in your home directory .fgfsrc when it tries to start. You can put any startup flags that you want into that file. For example, if you put --fg-root=/path/to/data into that file, then you double click on src/FlightGear/src/Main/fgfs (or run it from the command line) then it should startup and run. Once it is built, you can move fgfs anywhere that you want, such as into the Applications folder. From: Martin Spott [EMAIL PROTECTED] Organization: home Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Newsgroups: list.flightgear-devel Date: Thu, 11 Nov 2004 22:00:48 + (UTC) To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X [EMAIL PROTECTED] wrote: Do you think you might be able to modify the mac os x docs for 0.9.6 especially with regard to updating make tools for a successful source build? I'd welcome any sort of submission for documentation updates. This would be a great idea to get me back to working on the manual sheee I'd be happy to accept simple text and I will take care of converting this into LaTeX to match the existing layout, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
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
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
From: Arthur Wiebe [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 11 Nov 2004 13:41:58 -0500 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X After setting two environment variables I was able to get simgear 0.3.7 to compile without any problems. In bash you would set them like this: export CFLAGS=-I/usr/X11R6/include export CXXFLAGS=-I/usr/X11R6/include And I built plib 1.8.3 with help from the diffs you sent but building from CVS worked for me without any patching. I guess that means that the appropriate patches are already in the plib CVS, just not yet released. Now FlightGear itself is another story. I had to upgrade automake in order to run the autogen.sh script successfully. That is very strange, because I did not have to. I wonder what is different about our setups? I have not yet got FlightGear 0.9.6 to compile. Keep on getting: -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 What is also strange is that I can get FG to compile, up to the final link stage. I think that is the same problem that you are having, but we are getting different Undefined symbols. Mine seem to be from stuff that I have already built (plib). I will now try to get FlightGear from CVS to build. Not that I think it will work. On Thu, 11 Nov 2004 10:24:45 -0800, Adam Dershowitz [EMAIL PROTECTED] wrote: And were you able to get it all to build fine without any patches? As I said in the other Mac OS X thread, I had to make a few changes to get plib and SimGear to compile. And then I got it all to compile but the final link of FlightGear fails with some undefined symbols. These are things that should be in the library files that were already built. I am using gcc 3.3, automake 1.6.3 and autoconf 2.53 (these are the standards that are included with Xcode 1.5). And all fresh CVS code. -- Adam From: [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 11 Nov 2004 12:22:52 -0500 To: [EMAIL PROTECTED] Subject: [Flightgear-devel] Re: FlightGear on Mac OS X Arthur, Makefile.in isn't in CVS. It is generated by automake. GNU Automake - http://www.gnu.org/software/automake Freeware - Generates makefile.in files from makefile.am input files, as part of the official GNU coding standards and build process. Requires GNU autoconf. On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] wrote: are you running ./autogen.sh without an errors? Have you updated aclocal and autoconf also? I just did a make clean and a plib build from cvs and it worked fine under Mac os X (10.6). The rest of the build went ok also (simgear and flightgear) though I had a modified (flightgear) Input/input.cxx and Main/options.cxx. The FlightGear changes are for debugging some things I was looking at at one time... I'm doing a 'make clean install' for SimGear and FlightGear now from latest (1700 GMT) cvs. My plib and simgear are straight from cvs, flightgear and data are straight from cvs (no modified local copies, except for the FlightGear input.cxx and options.cxx files that I mentioned above). Ima Message: 8 Date: Thu, 11 Nov 2004 09:51:09 -0500 From: Arthur Wiebe [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X To: FlightGear developers discussions [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII Since I was getting nowhere trying to build FG 0.9.6 I checked it out from CVS instead. After getting automake 1.9.3 I was able to run autogen.sh and configure but it seems Makefile.in is missing in CVS. configure: 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 -- Arthur/ ___ 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
From: Curtis L. Olson [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 11 Nov 2004 13:09:21 -0600 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X Adam Dershowitz wrote: From: Arthur Wiebe [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 11 Nov 2004 13:41:58 -0500 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X After setting two environment variables I was able to get simgear 0.3.7 to compile without any problems. In bash you would set them like this: export CFLAGS=-I/usr/X11R6/include export CXXFLAGS=-I/usr/X11R6/include And I built plib 1.8.3 with help from the diffs you sent but building from CVS worked for me without any patching. I guess that means that the appropriate patches are already in the plib CVS, just not yet released. Now FlightGear itself is another story. I had to upgrade automake in order to run the autogen.sh script successfully. That is very strange, because I did not have to. I wonder what is different about our setups? I have not yet got FlightGear 0.9.6 to compile. Keep on getting: -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 What is also strange is that I can get FG to compile, up to the final link stage. I think that is the same problem that you are having, but we are getting different Undefined symbols. Mine seem to be from stuff that I have already built (plib). Did you build plib with the same version of the compiler you are using to build everything else? Different compilers (and compiler versions) can do the c++ name munging differently which can result in undefined symbols at link time. At compile time, the compiler just reads the file.h, but at link time it tries to match up requested functions with anything in any of the specified libraries. But if the library is compiled with a different version of the compiler, the requested symbol might not match the published symbols in the library and so things end up not being resolved at the link phase. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Yup, all built with gcc 3.3. Early on I followed the users guide which says that 2.95 is required. But I delete all of my object code and libraries, then rebuilt. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
I finally got it all to build and work! Curt, you were correct, despite what I said below. Seems that when I rebuilt everything, it was not actually everything. I somehow missed a few things. I think that the specific problem was that clouds3d is one directory deeper than most other things, and I believe that I just did not clear out the object files, or the library, that was there before I redid the build. So it was trying to link against the version of that one library that I had built with 2.95.2. Once I cleared that up, it seems that it all did build as advertised, except that I did do those couple of patches to plib. But Arthur says that using the CVS instead of the download of that will make that problem go away as well. I should try that. Thanks for all of the help and suggestions. FlightGear is a great program! -- Adam From: Adam Dershowitz [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 11 Nov 2004 11:25:14 -0800 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X From: Curtis L. Olson [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 11 Nov 2004 13:09:21 -0600 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X Adam Dershowitz wrote: From: Arthur Wiebe [EMAIL PROTECTED] Reply-To: FlightGear developers discussions [EMAIL PROTECTED] Date: Thu, 11 Nov 2004 13:41:58 -0500 To: FlightGear developers discussions [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X After setting two environment variables I was able to get simgear 0.3.7 to compile without any problems. In bash you would set them like this: export CFLAGS=-I/usr/X11R6/include export CXXFLAGS=-I/usr/X11R6/include And I built plib 1.8.3 with help from the diffs you sent but building from CVS worked for me without any patching. I guess that means that the appropriate patches are already in the plib CVS, just not yet released. Now FlightGear itself is another story. I had to upgrade automake in order to run the autogen.sh script successfully. That is very strange, because I did not have to. I wonder what is different about our setups? I have not yet got FlightGear 0.9.6 to compile. Keep on getting: -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 What is also strange is that I can get FG to compile, up to the final link stage. I think that is the same problem that you are having, but we are getting different Undefined symbols. Mine seem to be from stuff that I have already built (plib). Did you build plib with the same version of the compiler you are using to build everything else? Different compilers (and compiler versions) can do the c++ name munging differently which can result in undefined symbols at link time. At compile time, the compiler just reads the file.h, but at link time it tries to match up requested functions with anything in any of the specified libraries. But if the library is compiled with a different version of the compiler, the requested symbol might not match the published symbols in the library and so things end up not being resolved at the link phase. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Yup, all built with gcc 3.3. Early on I followed the users guide which says that 2.95 is required. But I delete all of my object code and libraries, then rebuilt. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Building FlightGear on Mac OSX
I have been trying to build FlightGear 0.96 (CVS) on a Mac, and have been using fgdev, and have followed the instructions in the FG users guide, as well as the instructions included in fgdev, but I have run into a bunch of problems. Any help that anyone can offer would be greatly appreciated. I have searched the lists and see that some others have had some of the same problems, but I have not found postings of solutions. I guess that the instructions for building on a Mac in the users guide are somewhat out of date. I am using OSX 10.3.5 and I have Xcode 1.5 installed (gcc 3.3 and gcc 2.95.2). The insructions say to use gcc 2.95, so I have started with that. I also am using tcsh as instructed (which is no longer the Mac default). First I found that by default I already had the versions of automake and autoconf that the instructions say to build, so I did not do that. (1.6.3 and 2.53 respectively) I had trouble getting plib to build, but, after a few changes, got it to compile. The instructions next call for building metakit, but I assume that is now included in SimGear? Building SimGear failed with gcc 2.95. When I switched to 3.3 it got much further, but failed on testserial. I was hoping that this is not critical. So next I tried to build FlightGear itself: ./configure --prefix=$BUILDDIR --without-threads --without-x configure: error: cannot run /bin/sh ./config.sub I found that the reason is that config.sub does not exist. Shouldn't autogen.sh create this file? Did I do something wrong? (I see that someone else had the same problem and posted to the mailing list, but I could not find a response). So, where I think I stand is: I have plib, I think that I have SimGear? I have downloaded and installed OpenAL and I can't get FG itself to even start to compile. Thanks, -- Adam ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
