RE: [Flightgear-devel] Building on Cygwin
I have the same problem with Main/renderer.cxx. Your solution (or one very like it) solves the problem. I guess near/far are reserved words in Cygwin? Thereafter, FGFS compiles and runs under Cygwin. I'm not using Andy's libs, but those built by Norman, with a couple of tweaks which have been listed recently (although these may not now be needed, since OpenAl has reportedly fixed the problems). Your errors seem to be lib-related so perhaps the solution lies there. Norman's libs are available at: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz Regards, Vivian Thanks for the pointer to the Norman's libs. I had been looking for those but could not find them anywhere. It appears that it is working now. How are Andy's libs meant to be used? One point I have discovered, is that (on Cygwin at least) the shortcut to your home directory, ~/, doesn't seem to get parsed properly when setting fg-root: [EMAIL PROTECTED] ~ $ fgfs --fg-root=~/FGFS/FlightGear/data/ Base package check failed ... Found version [none] at: ~/FGFS/FlightGear/data/ Please upgrade to version: 0.9.8 [EMAIL PROTECTED] ~ $ fgfs --fg-root=/home/Richard.Bytheway/FGFS/FlightGear/data/ ...(normal startup) Thanks again. Richard This e-mail has been scanned for Bede Scientific Instruments for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Building on Cygwin
Richard Bytheway wrote I have the same problem with Main/renderer.cxx. Your solution (or one very like it) solves the problem. I guess near/far are reserved words in Cygwin? Thereafter, FGFS compiles and runs under Cygwin. I'm not using Andy's libs, but those built by Norman, with a couple of tweaks which have been listed recently (although these may not now be needed, since OpenAl has reportedly fixed the problems). Your errors seem to be lib-related so perhaps the solution lies there. Norman's libs are available at: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz Regards, Vivian Thanks for the pointer to the Norman's libs. I had been looking for those but could not find them anywhere. It appears that it is working now. How are Andy's libs meant to be used? Hmmm ... never made them work, and I'd quite forgotten them. One point I have discovered, is that (on Cygwin at least) the shortcut to your home directory, ~/, doesn't seem to get parsed properly when setting fg-root: [EMAIL PROTECTED] ~ $ fgfs --fg-root=~/FGFS/FlightGear/data/ Base package check failed ... Found version [none] at: ~/FGFS/FlightGear/data/ Please upgrade to version: 0.9.8 [EMAIL PROTECTED] ~ $ fgfs --fg-root=/home/Richard.Bytheway/FGFS/FlightGear/data/ ...(normal startup) Never noticed that; I keep FGFS at a higher level, but now that you mention it, so it does. It's not a problem, but we ought to record all this somewhere. We seem to go through some Cygwin drama every major update. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [Flightgear-cvslogs] CVS: data/Aircraft/fokker100/Models
Hello Erik, Erik Hofman wrote: Update of /var/cvs/FlightGear-0.9/data/Aircraft/fokker100/Models In directory baron:/tmp/cvs-serv14144 Modified Files: f70_cabin.ac fokker70.ac fokker70.xml Log Message: Some final changes, fixes and updates for some time The model looks very nice and the handling feels pretty easy. It's only that I'm missing the cabin door being coupled to the parking brake as it was in your first version ;-) Cheers, 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
Re: [Flightgear-devel] Building on Cygwin
Vivian Meazza wrote: Never noticed that; I keep FGFS at a higher level, but now that you mention it, so it does. It's not a problem, but we ought to record all this somewhere. We seem to go through some Cygwin drama every major update. That's what Wiki's are for: http://www.seedwiki.com/wiki/flight_gear/flight_gear_developer_documentation.html?wpid=123227 Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: data/Aircraft/fokker100/Models
Martin Spott wrote: The model looks very nice and the handling feels pretty easy. It's only Thanks. that I'm missing the cabin door being coupled to the parking brake as it was in your first version ;-) No, it's not ... :-) Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs]
Erik Hofman wrote: Martin Spott wrote: that I'm missing the cabin door being coupled to the parking brake as it was in your first version ;-) No, it's not ... Hmmm, I don't understand: Did you decouple the cabin door from the parking brake intentionally because you thing the coupling is 'wrong' or does it actually work at your end ? At least I strongly believe the version that is in current CVS does _not_ have this coupling, 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
Re: [Flightgear-devel] Building on Cygwin
From: Andy Ross Vivian Meazza wrote: I have the same problem with Main/renderer.cxx. Your solution (or one very like it) solves the problem. I guess near/far are reserved words in Cygwin? Goodness, that brings back memories. The near and far keywords are holdovers from 16 bit DOS compilers. They are still defined (as noops) for compatibility with ancient code. Basically, the 8086 had 16 bit registers, so a single instruction could only address memory within a 64k range (which was defined by the appropriate segment register). This 16 bit object was called a near pointer. If you wanted to see things outside that range, you needed to use multiple instructions to first load a segment register and then execute the load. (This really wasn't so insane if you think about it -- the original idea for a typical was that all the code would go in a 64k segment, the heap data in another and the stack in a third; this 192k address space was larger than that available to Unix programs running on a PDP-11, for instance. It seemed like a good solution at the time. It didn't become a problem until typical interactive PC applications started needed hundreds of kilobytes of address space. For 1976, it was actually pretty elegant.) I can remember the pain too :-). Actually it was a limitation of what could be made for hardware at the time (which I think you already know). The 16 bit address register (max 64k value) was a pretty cool step up, and quite a dramatic improvement over the 8 bit especially in micro chips. (As was the 32 later). The addressing scheme was merely a comprimise for what could be done. The orginization of IBM PC Bios layout on the other hand was a design choice based on expectations of what would be possible for the architecture in 1980 vision. And that sure caused some pain! Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Building on Cygwin
Erik Hofman wrote Vivian Meazza wrote: Never noticed that; I keep FGFS at a higher level, but now that you mention it, so it does. It's not a problem, but we ought to record all this somewhere. We seem to go through some Cygwin drama every major update. That's what Wiki's are for: http://www.seedwiki.com/wiki/flight_gear/flight_gear_developer_documentati on.html?wpid=123227 Of course, in keeping with custom, when I wrote 'we', I meant 'someone else' :-) Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: plib viewer
* Josh Babcock -- Wednesday 30 March 2005 18:34: Has anyone gotten the viewer program from the plib-examples package running? When I compile and run it I get: WARNING: fntLoadTXF: Failed to open 'data/default.txf' for reading. Works perfectly. And the font is in CVS: $ grep default.txf ~/fgfs/plib/examples/src/ssg/viewer/data/CVS/Entries /default.txf/1.9/Thu May 22 14:06:05 2003/-kb/ If it's not in your checkout, you know what to do. :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Building on Cygwin
* Erik Hofman -- Thursday 31 March 2005 13:27: That's what Wiki's are for: http://www.seedwiki.com/wiki/flight_gear/flight_gear_developer_documentation.html?wpid=123227 That's really where the FAQ should be maintained, too, as long as someone is regularly archiving the contents. (I tried with wget, but it failed because it doesn't like the space in Flight Gear.) I would certainly contribute to a FAQ there, but am not keen to take over the whole FAQ maintainership. (I'm only interested and knowledgable in some fgfs (on Linux) topics, but don't care for others, let alone other operating systems.) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Building on Cygwin
Melchior FRANZ wrote: * Erik Hofman -- Thursday 31 March 2005 13:27: That's what Wiki's are for: http://www.seedwiki.com/wiki/flight_gear/flight_gear_developer_documentation.html?wpid=123227 That's really where the FAQ should be maintained, too, as long as someone is regularly archiving the contents. (I tried with wget, but it failed because it doesn't like the space in Flight Gear.) I would certainly contribute to a FAQ there, but am not keen to take over the whole FAQ maintainership. (I'm only interested and knowledgable in some fgfs (on Linux) topics, but don't care for others, let alone other operating systems.) We recently lost our FAQ maintainer. It would be great if someone would be willing to step forward and contribute on this front. You don't need to be a flightgear expert, just someone willing to catalog and document common questions and answers ... basically watch for people commenting that such and such should really be in the FAQ and then putting it there. Best regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: fgjs bug
Fridtjof Busse wrote: I'd say the X52 then has exactly this problem. One bit is always on, since it has a mode-switch (doesn't do anything without the windows-software) which always has a bit set. You can write a joystick definition to use that mode switch however you want; on all systems. Take a look at the X45.xml file for an example. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: fgjs bug
* Andy Ross [EMAIL PROTECTED]: I'd say the X52 then has exactly this problem. One bit is always on, since it has a mode-switch (doesn't do anything without the windows-software) which always has a bit set. You can write a joystick definition to use that mode switch however you want; on all systems. Take a look at the X45.xml file for an example. That's true, but the original use for the Switch on the X52 is to switch profiles during the game, that's what the LCD on the throttle is for. But this is only supported by the windows-software. Only the stop-watch works out-of-the-box. IMHO the X45 didn't have a LCD. And for me, the bit set due to the switch is just causing trouble :) It would still be nice to have fgjs only check for changed bits, not activated ones. -- Fridtjof Busse I don't think we need to be subliminable about the differences between our views on prescription drugs. George W. Bush September 12, 2000 Quoted by Slate magazine from comments in Orlando, Florida. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
