Hi Guys, Few months back we spent a couple days trying to compile FG on Windows using the FG Wiki and did not have any luck. This is a very frustrating point for people who only work with windows and would like to contribute but don't have a clear document or path on how to make this work.
Geoff, I appreciate your efforts in creating your own custom build process but we could not get your files to work. I'm sure there are many developers running Windows that can provide effective contribution to this project but can't because of the difficult build process. Can someone explain why this has not been addressed? Thanks! Christian FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: christ...@freedomworks.ca www.FreedomWorks.ca -----Original Message----- From: stan.mar...@l-3com.com [mailto:stan.mar...@l-3com.com] Sent: Friday, February 26, 2010 2:29 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] build on Windows; dependencies? Csaba and Geoff, Thanks for your replies. I should have specified that I am trying to build FlightGear 1.9.1, downloaded 2/3/2010 from flightgear.org at which time it was the most current release (I see 2.0.0 is now out). I initially started to build just SimGear, same version, downloaded from www.simgear.org on the same day, using the similar solution file found under simgear/projects/VC8. I am using the VS8 solution files found in the projects subdirectory (projects/VC8) to build both FlightGear and SimGear. Pthreads is needed in SimGear sgthread.hxx. Per Geoff's post, they are required for SGThread. As you say, if SGThread is no longer required, it could be deleted and the dependency on pthread thereby removed. Meanwhile I downloaded POSIX Threads for Win32 from http://sourceware.org/pthreads-win32/ which got me over that problem. The Boost library was procured and having the headers solved my build issues. I'll still gently suggest that maybe Boost should be avoided if the use is minimal, which it currently is. If there is consensus in the community that it should be used, then it probably should be used extensively. Might as well! I am having another problem with 1.9.1, however. The project for FlightGearLib includes a number of files which appear to have moved in the download source tree. All were supposedly under the src/ATC path. They seem to have moved to src/ATCDCL directory instead. Here are the offenders: AIEntity.cxx AIGAVFRTraffic.cxx AILocalTraffic.cxx AIMgr.cxx AIPlane.cxx approach.cxx ATC.cxx ATCDialog.cxx ATCmgr.cxx ATCProjection.cxx ATCutils.cxx ATCvoice.cxx atis.cxx commlist.cxx ground.cxx tower.cxx transmission.cxx transmissionlist.cxx A few other files are turning up missing as well: src/FDM/Balloon.cxx src/fdm/balloon/BalloonSim.cpp src/FDM/MagicCarpet.cxx src/Scenery/newcache.cxx src/GUI/puList.cxx src/GUI/sgVec3Slider.cxx src/Scenery/tileentry.cxx src/Airports/trafficcontrol.cxx src/Main/FGManipulator.cxx trafficcontrol.cxx appears to be the lone occupant of src/ATC. I haven't found the others yet. Stan ---------------------------------------------------------------------------- -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel