[Flightgear-devel] Inner marker sound
Is there anyway of stopping the inner marker sound going off whenever starting at an airport on the runway? This is a bug I presume because I do not know of any inner markers located directly on the runway thresholds and it stops once the sim is loaded. I have to turn my sound down when starting FG, it's so loud. Paul ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] gcc seg faults building 0.9.6 under FC2
Has anyone else seen this? if g++ -DHAVE_CONFIG_H -I. -I. -I../../../src/Include -I../../.. -I../../../src -I/usr/X11R6/include -I/usr/local//include -g -O2 -D_REENTRANT rs.o -MD -MP -MF ".deps/uiuc_warnings_errors.Tpo" -c -o uiuc_warnings_errors.o uiuc_warnings_errors.cpp; \ then mv -f ".deps/uiuc_warnings_errors.Tpo" ".deps/uiuc_warnings_errors.Po"; else rm -f ".deps/uiuc_warnings_errors.Tpo"; exit 1; fi In file included from /usr/include/c++/3.3.3/locale:47, from /usr/include/c++/3.3.3/bits/ostream.tcc:37, from /usr/include/c++/3.3.3/ostream:535, from /usr/include/c++/3.3.3/iostream:45, from uiuc_warnings_errors.h:8, from uiuc_warnings_errors.cpp:78: /usr/include/c++/3.3.3/bits/locale_facets.h: In instantiation of `std::time_put_bynamehttp://bugzilla.redhat.com/bugzilla> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. make[3]: *** [uiuc_warnings_errors.o] Error 1 make[3]: Leaving directory `/home/kmacy/FlightGear-0.9.6/src/FDM/UIUCModel' make[2]: *** [all-recursive] Error 1 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New scenery build
Arnt Karlsen wrote: On Fri, 03 Dec 2004 14:40:12 -0600, Curtis wrote in message <[EMAIL PROTECTED]>: ..the size, is like last one, or will this new build be much bigger than the 0.9.5 scenery? (~12.6G) I haven't looked closely, but it should be pretty similar. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New scenery build
On Fri, 03 Dec 2004 14:40:12 -0600, Curtis wrote in message <[EMAIL PROTECTED]>: ..the size, is like last one, or will this new build be much bigger than the 0.9.5 scenery? (~12.6G) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New scenery build
Jason Cox wrote: Curt, In my on going quest to compile local scenery, I was wondering if you just run a script that makes all the scenery or do you do each step individualy ? If you do run a script, is it posible for you to release it to the list or on FlightGear ? thanks jason cox Jason, I typically run the individual "prep" tools by hand ... and for the most part, once that's done, it's done and I don't have to do it again unless the underlying data changes (i.e. an update to vmap0 is released, or an update to SRTM, etc.) And in that case, I just have to re-prep that particular data set. The one item that changes frequently is the airport data, but I run that tool by hand as well. For the final scenery assembly, all the frontend scripts I run are in the src/BuildTiles/Parallel/ directory. This allows me to run a task server to manage the build (or a portion of it) and then I can throw as many clients as I have available at the job of actually building scenery. This is very disk io intensive though so it's not as conducive to massively distributing the work (like SETI for instance.) 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 [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New scenery build
Curt, In my on going quest to compile local scenery, I was wondering if you just run a script that makes all the scenery or do you do each step individualy ? If you do run a script, is it posible for you to release it to the list or on FlightGear ? thanks jason cox On Thu, 2004-12-02 at 21:47 -0600, Curtis L. Olson wrote: > I am currently working on building the latest round of world scenery for > FlightGear. I'm not done, so don't consider this to be the "official" > announcement. However, for those that want to get a jump on the > competition, you can find the new scenery here: > > ftp://ftp.flightgear.org/pub/fgfs/Scenery-0.9.7/ > > This scenery should work just fine with the 0.9.6 version, but some > radio towers will look better running with the current CVS version of FG > ... not a big deal. > > There is nothing ground breaking in this new build. It is mostly a > collection of small fixes, and is based on the latest[1] airport data > from Robin Peel including many submissions from FG developers and > users. I've done quite a bit of addition work on airport surfaces so > the little odd cliffs that showed up in a few places mid-runway should > now be gone. > > [1] Well, the latest data as of the start of my build ... figures he > would release an update before I was finished, but I'm past the point of > no return now. > > Regards, > > Curt. > ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Solaris/GPU recommendations sought!
Gerhard Wesp wrote: > I thought about Solaris. Seems to be absolutely straightforward to > install. But I don't know anything about OpenGL and GPU support. > Linux: X11 installation (especially GPU drivers) were a pain last time > I checked (requires kernel compile!). Has this changed in the > meantime. Other options? FreeBSD perhaps? I'm not sure what trouble you had, but the NVidia drivers are almost idiot-proof these days. Install your Linux distribution (I use FC3 and can recommend it; others will work great too), then download the driver package and run it. One of the third party RPM distributors (livna.org maybe?) used to have it packaged automatically so you could just do something like "yum update nvidia" to download and install it automagically. The ATI drivers are not so pleasant, however (the last I checked, the still lacked support for the 2.6 kernel). Although the built-in DRI drivers for the ATI 8x00 and 9200 cards run flightgear very well and come standard with your X server. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FGNetFDM etc.
Gerhard Wesp wrote: > 1. GNU C++ structure layout may _differ_ between different compiler > _minor_ versions. E.g., one sizeof() was 504 bytes on Linux with > g++ 3.3.3 and 520 bytes on Cygwin with g++ 3.3.1. Both on x86. Are you sure? Starting with the 3.2.x releases, g++ is supposed to have standardized on a single C++ ABI. Are you sure the two builds didn't have differing flags? The Cygwin headers, I know, have a bunch of win32-compatibility hacks that tend to muck with standards compliance. That said, basing a protocol on the idea of spitting raw structures onto the network is kind of a silly idea, for exactly the reasons you posit. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] cvs tools
KDE's development module kdesdk contains lots of useful cvs utility scripts. I extracted those also useful for fgfs developers and put them here: http://members.aon.at/mfranz/cvstools.tar.gz (16 kB) I very often use the first five of the following list. ($HOME/bin/cvs is actually a link to colorcvs.) m. Here's a list of contents: -- colorcvscvs wrapper that colors output cvs-clean removes all files that were not downloaded via cvs (to remove generated files; handle with care!) cvslastchange launches "cvs diff -u" to display the last applied changes for a given file. HEAD branch only. cvslastlog Shows the log associated with the last change on a given file. cvscheckOffline check for status of files in a checked-out (very useful to find files with sticky tags/dates) cvschanged Check for edited or merged files in a checked out CVS module, without connecting to the CVS server. cvsblameBonsai-like cvs annotate (opens "cvs ann" in browser; change last line if you don't have konqueror) cvsrevertlast Reverts all the files given on the command by one version, then you can commit them. cvsaddcurrentdir Add all files in and below the current dir to cvs. *.c, *.h, *.C, *.cpp, *.cc are added automatically, *~, *.o, *.so, *.lo, *.la, .libs/, .deps/, .#* are ignored. You will be asked for the remaining files. noncvslist List all files in a checked out CVS module that are unknown to to the CVS server. cvsversion Display CVS version of a file without connecting to the server. (also used by the other scripts) cvsremovealltags Remove all tags from a CVS file. Use with care, and for instance after copying a file on the server. cvsbackport Backport the last commit in HEAD, to a branch. cvsforwardport Forwardport the last commit in a branch to HEAD pruneemptydirs Detects stale source dirs in a CVS tree cvslastreferenced Goes through the whole history of a file to find all modifications referencing a specific string. It's useful if you want to know when a function has been removed/modified/added to a file if a recent cvs annotate doesn't reference it anymore. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Solaris/GPU recommendations sought!
On Fri, 3 Dec 2004 16:03:13 +0100 [EMAIL PROTECTED] (Gerhard Wesp) wrote: Primary objective is to run FlightGear rock solidly (need it as a front end/testing environment) for my own FDM). Why your own FDM? Don't get me wrong - I think there are a lot of reasons why someone would want to write their own FDM. One reason is because it's fun (OK, I'm wierd :-) But, if your being driven to write your own because one of the others is lacking something or there is some other cause, I'd be interested to hear it, for the purpose of possibly making improvements. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Solaris/GPU recommendations sought!
Gerhard Wesp wrote: sorry if this is a bit off-topic, but it's solely related to getting FG to work! I'd like to run it on some x86 UNIX variety. Primary objective is to run FlightGear rock solidly (need it as a front end/testing environment) for my own FDM). Second one is ease of install of UNIX on hardware. 3rd is graphics performance. I thought about Solaris. Seems to be absolutely straightforward to install. But I don't know anything about OpenGL and GPU support. Linux: X11 installation (especially GPU drivers) were a pain last time I checked (requires kernel compile!). Has this changed in the meantime. Other options? FreeBSD perhaps? Gerhard, I can share my thoughts based on my own experience. I'm not saying there aren't equivalent or even better ways to go, I'm just sharing my experiences. 1. These days I'm tempted to say that overall system stabililty is more a product of rock solid hardware than of the OS. Linux has been solid for many many years (as has been solaris) and recent versions of windows is pretty good now too as long as you avoid connecting it up to the internet. But I see much more instability do to questionable hardware than to questionable operating systems. 2. That said, I've been really happy with the stability of Linux. At the AOPA we had 4 copies of FG running on 4 PC's (networked together) and ran these for 3 days (shutting down at the end of each day.) But we started FG up at the beginning of the day and ran it straight through to the end. The computes, the OS, and FG was rock solid the entire time. I remember having to restart all the software once on one of the days, but I can't remember why now, I remember that I did not blame it on FG though ... we might have wanted to change the configuration or something? FG ran through all kinds of abuse, crashing into the ground, reseting positions around the USA over and over again. I thought it was a pretty good stress test and FG/Linux performed flawlessly through all this abuse. 3. I've been messing around with Fedora Core 2/3 a bit lately for my desktop machines. The nvidia drivers are a breeze to install once you figure out a couple little tricks ... a) download the linux drivers from the nvidia.com web site b) go to a text console (ctrl-alt-f1), log in as root and run "init 3" c) the linux driver comes as a "sh" script so type "sh NVIDIA_DRIVER_FILE_NAME" d) answer the questions e) edit your /etc/X11/xorg.conf file and change the "nv" driver to "nvidia" f) run "init 5" to start up x11 again, and watch for the nvidia splash screen which is a good indication that everything installed correctly. g) if you run apt-get or up2date and load new versions of X11, you probably will need to reinstall the nvidia drivers because some of the nvidia files can get overwritten. f) you need to make sure the kernel module is installed ... that works out of the box with the default installed kernel, but if you upgrade the kernel (asside from needing to install the nvidia drivers again to get the correct module built for your kernel) you may run into trouble with your system autoloading the nvidia kernel module. In that case I've been able to create an /etc/rc.modules file (with 755 permissions) and put a single line in it that says "modprobe nvidia". So installing the nvidia drivers on a vanilla fedora system is dead simple. If you start upgrading kernels or x11 you may need to put in a little more effort, but it's still not all that hard. 4. I haven't played around with solaris for a long time. We have had someonen contribute an solaris x86 build of FG so I know it work, but I don't know the driver situation. FreeBSD is a pretty good option, but my sense is that FreeBSD is better suited to those that want to learn (or already know) a fair bit about unix. Recent Linux versions are getting pretty good at hiding the hard sys-admin stuff from you and making system setup and maintanance pretty accessible to non-computer geniuses, although it's still unix, so the more you know about unix, the more you can tweak and the quicker you will find solutions to your issues. 5. It's been my experience with nVidia cards that overall graphics performance and overall FG performance is pretty equivalent between windows and unix given the exact same hardware. 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 [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FGNetFDM etc.
Gerhard Wesp wrote: Hi all, I also played around a little with the native-fdm and native-ctrls. I made the following observations: 4. There is an RFC 1014: XDR (external data representation) which basically defines big-endian integers and IEEE floating point values. Wouldn't we want to base the interface upon XDR? I think we should follow standards where available. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Solaris/GPU recommendations sought!
Gerhard Wesp wrote: Hi all, sorry if this is a bit off-topic, but it's solely related to getting FG to work! I'd like to run it on some x86 UNIX variety. Primary objective is to run FlightGear rock solidly (need it as a front end/testing environment) for my own FDM). Second one is ease of install of UNIX on hardware. 3rd is graphics performance. Does it need to be something you have laying around, and what price is acceptable? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] FGNetFDM etc.
Hi all, I also played around a little with the native-fdm and native-ctrls. I made the following observations: 1. GNU C++ structure layout may _differ_ between different compiler _minor_ versions. E.g., one sizeof() was 504 bytes on Linux with g++ 3.3.3 and 520 bytes on Cygwin with g++ 3.3.1. Both on x86. 2. One can force the structs into same size by using the GNU-specific attribute __attribute__ (( packed )). 3. GNU compilers ignore #pragma pack etc. 4. There is an RFC 1014: XDR (external data representation) which basically defines big-endian integers and IEEE floating point values. Wouldn't we want to base the interface upon XDR? Cheers -Gerhard -- Gerhard Wesp o o Tel.: +41 (0) 43 5347636 Bachtobelstrasse 56 | http://www.cosy.sbg.ac.at/~gwesp/ CH-8045 Zuerich \_/ See homepage for email address! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
It was my fault. The solution in FlightGear/cvs/FlightGear/FlightGear-2.sln is supposed to compile all you need for FlightGear. You just have to get software in the structure below : FlightGear/cvs/FlightGear <= FlightGear FlightGear/cvs/SimGear<= SimGear FlightGear/cvs/plib <= plib FlightGear/zlib-1.1.4 <= zlib pthread-snap-2004-06-22 <= pthread for win32 The zip file reflect this structure. -Fred Quoting RENNUIT Antoine 203220 Thésard : > Now it works, sorry for disturbing... > > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] la part de RENNUIT > Antoine 203220 Thésard > Envoyé : vendredi 3 décembre 2004 14:59 > À : 'FlightGear developers discussions' > Objet : RE: [Flightgear-devel] MSVC > > > I cannot download the new file... > > > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] la part de Frederic > Bouvier > Envoyé : vendredi 3 décembre 2004 14:54 > À : FlightGear developers discussions > Objet : Re: [Flightgear-devel] MSVC > > > Quoting Erik Hofman : > > > RENNUIT Antoine 203220 Thésard wrote: > > > Hello, > > > > > > I am new to flight gear. I am looking for a "how to" to compile FG under > > > MSVC (either 6 or .net) : at the moment I am completely lost in all the > > > libraries needed to link : how come these libraries (simgear, plib, > zlib, > > > metakit, openAL...) do not broadcast with simple .lib files??? I read > > > several threads from the forum, but did not find enough information to > go > > > on. > > > > You can find MSVC (7.0) project files here: > > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ > > I've just made an update today with current project files for .NET 2003. > Obviouly, path have to be changed. > > -Fred > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Solaris/GPU recommendations sought!
Hi all, sorry if this is a bit off-topic, but it's solely related to getting FG to work! I'd like to run it on some x86 UNIX variety. Primary objective is to run FlightGear rock solidly (need it as a front end/testing environment) for my own FDM). Second one is ease of install of UNIX on hardware. 3rd is graphics performance. I thought about Solaris. Seems to be absolutely straightforward to install. But I don't know anything about OpenGL and GPU support. Linux: X11 installation (especially GPU drivers) were a pain last time I checked (requires kernel compile!). Has this changed in the meantime. Other options? FreeBSD perhaps? Thanks a lot -Gerhard -- Gerhard Wesp o o Tel.: +41 (0) 43 5347636 Bachtobelstrasse 56 | http://www.cosy.sbg.ac.at/~gwesp/ CH-8045 Zuerich \_/ See homepage for email address! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
Now it works, sorry for disturbing... -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de RENNUIT Antoine 203220 Thésard Envoyé : vendredi 3 décembre 2004 14:59 À : 'FlightGear developers discussions' Objet : RE: [Flightgear-devel] MSVC I cannot download the new file... -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Frederic Bouvier Envoyé : vendredi 3 décembre 2004 14:54 À : FlightGear developers discussions Objet : Re: [Flightgear-devel] MSVC Quoting Erik Hofman : > RENNUIT Antoine 203220 Thésard wrote: > > Hello, > > > > I am new to flight gear. I am looking for a "how to" to compile FG under > > MSVC (either 6 or .net) : at the moment I am completely lost in all the > > libraries needed to link : how come these libraries (simgear, plib, zlib, > > metakit, openAL...) do not broadcast with simple .lib files??? I read > > several threads from the forum, but did not find enough information to go > > on. > > You can find MSVC (7.0) project files here: > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ 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] MSVC
I cannot download the new file... -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Frederic Bouvier Envoyé : vendredi 3 décembre 2004 14:54 À : FlightGear developers discussions Objet : Re: [Flightgear-devel] MSVC Quoting Erik Hofman : > RENNUIT Antoine 203220 Thésard wrote: > > Hello, > > > > I am new to flight gear. I am looking for a "how to" to compile FG under > > MSVC (either 6 or .net) : at the moment I am completely lost in all the > > libraries needed to link : how come these libraries (simgear, plib, zlib, > > metakit, openAL...) do not broadcast with simple .lib files??? I read > > several threads from the forum, but did not find enough information to go > > on. > > You can find MSVC (7.0) project files here: > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re : MSVC
There are many .lib files associated (net_d, ssg_d, sl_d, pui_d, fnt_d, js_d, ul_d ssgAux_d, SimGear_d, zlib, pThreadVC...) to be linked with the project. How did you obtain them? I cannot find them in the downloaded simgear files... Did you compile the .lib files on your own? Moreover, I cannot find where you use pLib... -Message d'origine- De : RENNUIT Antoine 203220 Thésard Envoyé : vendredi 3 décembre 2004 10:51 À : 'FlightGear developers discussions' Objet : MSVC Hello, I am new to flight gear. I am looking for a "how to" to compile FG under MSVC (either 6 or .net) : at the moment I am completely lost in all the libraries needed to link : how come these libraries (simgear, plib, zlib, metakit, openAL...) do not broadcast with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. Thanks, Antoine ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re : MSVC
There are many .lib files associated (net_d, ssg_d, sl_d, pui_d, fnt_d, js_d, ul_d ssgAux_d, SimGear_d, zlib, pThreadVC...) to be linked with the project. How did you obtain them? I cannot find them in the downloaded simgear files... Did you compile the .lib files on your own? Moreover, I cannot find where you use pLib... -Message d'origine- De : RENNUIT Antoine 203220 Thésard Envoyé : vendredi 3 décembre 2004 10:51 À : 'FlightGear developers discussions' Objet : MSVC Hello, I am new to flight gear. I am looking for a "how to" to compile FG under MSVC (either 6 or .net) : at the moment I am completely lost in all the libraries needed to link : how come these libraries (simgear, plib, zlib, metakit, openAL...) do not broadcast with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. Thanks, Antoine ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC
Quoting Erik Hofman : > RENNUIT Antoine 203220 Thésard wrote: > > Hello, > > > > I am new to flight gear. I am looking for a "how to" to compile FG under > > MSVC (either 6 or .net) : at the moment I am completely lost in all the > > libraries needed to link : how come these libraries (simgear, plib, zlib, > > metakit, openAL...) do not broadcast with simple .lib files??? I read > > several threads from the forum, but did not find enough information to go > > on. > > You can find MSVC (7.0) project files here: > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC
RENNUIT Antoine 203220 Thésard wrote: Hello, I am new to flight gear. I am looking for a "how to" to compile FG under MSVC (either 6 or .net) : at the moment I am completely lost in all the libraries needed to link : how come these libraries (simgear, plib, zlib, metakit, openAL...) do not broadcast with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. You can find MSVC (7.0) project files here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] MSVC
Hello, I am new to flight gear. I am looking for a "how to" to compile FG under MSVC (either 6 or .net) : at the moment I am completely lost in all the libraries needed to link : how come these libraries (simgear, plib, zlib, metakit, openAL...) do not broadcast with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. Thanks, Antoine ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RE: [Plib-devel] Re: [PATCH] crease for ac3d files and speedup
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Wolfram Kuss > Sent: Friday, December 03, 2004 4:05 AM > To: [EMAIL PROTECTED] > Subject: Re: [Plib-devel] Re: [PATCH] crease for ac3d files and speedup > > > Ok, committed. > > Bye bye, > Wolfram. The current PLIB tarball has been updated to reflect these changes http://plib.sourceforge.net/dist/current.tgz 638429 Dec 3 01:19 current.tgz Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
