Geoff,
I agree with all you have said, but would add the following: The reset bug has been sorted. The crash-on-exit bug has probably been sorted, but I haven't had time to test it yet. I don't see the red/orange effect you report. There is a binary here - a few days old, and using osg rev. 10753 - ftp://ftp.abbeytheatre2.org.uk/fgfs/executable/ It might be helpful if you could test it to see if it solves any of your bugs. Vivian -----Original Message----- From: Geoff McLane [mailto:ubu...@geoffair.info] Sent: 11 December 2009 12:37 To: FlightGear developers discussions Cc: joshua.c.stonestr...@ivv.nasa.gov Subject: Re: [Flightgear-devel] Flight Gear on Windows On Thu, 2009-12-10 at 11:29 -0500, Joshua C. Stonestreet wrote: RE: Building SG/FG in native MS Windows using MSVC You do not specifically state which MSVC build files you started with, but assume you used those in the respective SG/FG cvs or tar.gz sources? Nearly ALWAYS the MSVC build files are OUT-OF-DATE! This is a FAST changing project, and it is nearly IMPOSSIBLE to keep MSVC build files fully up-to-date! But that said, it is usually a simple matter to start with the current build files, and (a) delete files that no longer exist in the respective source, and (b) when you come to the link, if new files have been added to either SG or FG they will show up as unresolved externals, and you just search for where the particular functions is defined in the source, and ADD those new files to the respective projects. And while you do not particularly need to re-create exactly the same folder structure, not doing so will always mean making more adjustments in the MSVC IDE Property Pages -> Configuration Properties -> C/C++ -> General -> Additional Include Directories, and Linker -> General -> Additional Library Directories, and/or Linker -> Input -> Additional Dependencies. I have dedicated a section of my site to building flightgear, but it too will always be out-of-date, sometimes just hours after putting it there ;=)), and I now use a 'complete' - that is _ALL_ dependent sources - approach _NOT_ suited to all ;=(), especially since it depends on re-creating the EXACT folder structure for SOURCE and then copies everything to a WORK folder, using the SETUPFG.BAT file... but it works well for me ;=)) See :- http://geoffair.net/fg , specifically http://geoffair.net/fg/fgfs-047.htm , but many other pages with hopefully helpful hints... I too have NOT done an update for a while, due to some new systems (sound, shaders, etc) being modified/added recently, such that I have not yet been able to build a fully stable WIN32 version using MSVC9. Two important things hold me back at the moment, and they are :- (i) a red/orange (and sometimes dark) pall, overlay, over the scene in certain, very repeatable, circumstances, see - http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-orange-pall , and http://geoffair.net/tmp/fg/ , and (ii) using the reset causes a crash! The only other MSVC build file set I know about is here :- ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ - and the sub-directory - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ Maybe others could remind us of other MS WIN native, MSVC build help locations... and I read here and there some have good success with CygWin... But 'old' MSVC build files in native windows is a way of life in fast changing projects ;=)) Hope this helps. Geoff.
------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
