external: index
internal: preamble folders downloads ... end
PAGE UNDER CONSTRUCTION
2011-03-29: The BIG problem maintaining a set of MSVC build file for SimGear/FlightGear (SG/FG) is that the project is always very active, thus these become out-of-date quite quickly - so it becomes a maintenance nightmare! This has been massively improved with the advent of the Hudson (daily) build, so at least one MSVC build set is now well maintained.
So here I am ONLY talking about my own personal build set. For quite some time now I have been working on a set of Perl scripts that in some way act like the unix auto-tools. That is they read the 'configure.ac' file, and then process the set of 'Makefile.am' files. This started out with the venerable am2dsp.pl written by Curt yonks ago, but has progress to a fully re-written a amsrcs04.pl.
Since the primary SG/FG maintainer work in unix, this 'configure.ac/Makefile.am' file set is always up-to-date, so it means a NEW set of DSW/DSP MSVC build files can be built each time, from scratch. But naturally these perl scripts also need some help in finding things, so they need a well developed input response file to work from. Once such an input file has been built, which can be considered like a 'configuration' file, then this remains relatively stable.
Also my previous FG build system always re-built everything - that is all the dependencies first - here I offer two favors. Again one where all dependencies are built, but another where ONLY SG and FG are built. That is all the headers and libraries needed are stored in a single 3rdParty folder, and the only two components that need to be downloaded and built are Simgear and FlightGear, and of course FG is two parts - the source, and the base data.
Finally, I got sick of always having to arrange the OpenSceneGraph (OSG) many DLLs, so went for a static library build of OSG, and also shifted to a MSVC 'static' RUNTIME, /MT and /MTd. The previous builds always used the DLL RUNTIME, /MD and /MDd, so all the dependent libraries had to rebuilt using this 'static' RUNTIME.
This meant, to adopt this runtime change, a complete full fresh re-build of the DSW/DSP MSVC build files was needed, but this is now a piece of cake with amsrcs04.pl ;=)) Of course, to use this one MUST have 'perl' installed. Mine is from ActivePerl, and is relatively painless to install.
***TBD***
***TBD***
etc ...
***TBD***
But unfortunately this is about 15-20 days later, after a 'git pull', so a number of other changes had been made...
Date | Link | Size | MD5 |
---|---|---|---|
2011/04/16 | fg-src-20110416.zip | 3,504,957 | 68dbc23624648c608f2ed5b26be15ab2 |
2011/04/16 | sg-src-20110416.zip | 1,256,913 | 197313b78d56888d3cf1b0358c64e93e |
This is the fg data used with the above, with LOTS of 'Aircraft' data excluded. | |||
2011/04/16 | fg-data-20110416.zip | 435,824,588 | 0649ff76a7bc5c885ca3ace21c6db5b4 |
***TBD***
Take care downloading and running executables from the web!
Date | Link | Size | MD5 |
---|---|---|---|
2011/04/12 | fgfs-bin-20110402.zip | 6,719,580 | 7c29de8e491c8fc646484efb940f08b7 |
BUT, at this time I have YET to successfully build scenery using these 'tools'...
etc ...
PAGE UNDER CONSTRUCTION
EOP - developing fgfs-053.htm