Release process |
---|
|
Note The output files on Jenkins download.flightgear.org and sf.net should always be the same. Jenkins pushes them to download.flightgear.org from where they get distributed to sf.net (with some renaming-magic involved). Direct dowloads from Jenkins should be avoided as much as possible. [1] |
See Building FlightGear - Cross Compiling for the main article about this subject. |
mingw has came a long way, and i think the MXE openscenegraph package (currently at 3.2.1 on master!!), is beautifully maintained, now it builds almost all core libraries dynamically with some argument passing, even as a static target(MXE_TARGETS='i686-w64-mingw32.static'), but it's those plugins again, with their linking errors! i think these are because i'm using the i686-w64-mingw32.static-g++ compiler as opposed to the shared one... so as soon as i can get the shared build environment running and solve all of it's dependancies for OSG, i think we can have a cross compiller in our hands! — hamzaalloush (Thu May 14). Re: [SOLVED] Install osgEarth feature on Win7 64b with FG gi. (powered by Instant-Cquotes) |
We’ve improved the tool around daily build creation. Still some progress to be done but daily builds for Mac and Windows are uploaded to: https://sourceforge.net/projects/flightgear/files/unstable/ (And hence, all the SF mirrors) And also directly available from: http://download.flightgear.org/builds/nightly/ <http://download.flightgear.org/builds/nightly/>; The ‘latest’ files in that directory are stable symlink, I am currently writing a descriptive web-page which will point to them since we expect the patch version number to evolve during 3.5 development (and I will be testing this soon, mostly to see what breaks!) All the usual caveats about un-tested code apply - although we will probably add some warnings over time to the builds themselves (splash screen etc) to remind people they’re not using a stable release. — James Turner (2015-03-23). [Flightgear-devel] Daily builds update. (powered by Instant-Cquotes) |
The GUI launcher included in these builds includes a new dialog to setup (and remember) the FGRoot using file picker. It does some version checking to hopefully make things as robust as possible for the user. — James Turner (2015-03-26). Re: [Flightgear-devel] Download description page. (powered by Instant-Cquotes) |
Note Take care to mention that you're using a nightly build, and to specify when it was built (you can find details in FlightGear's Help > About dialog) |
git clone git://git.code.sf.net/p/flightgear/fgdata/
git clone git://git.code.sf.net/p/flightgear/fgdata/
/home/jenkins
, that's where we have plenty of free space disk on this machine.G:jenkins
, that's where we have plenty of free space disk on this machine.Windows-release
, Mac-release
and Linux-release
have to be triggered by-hand. The result is automatically uploaded to http://fgfs.goneabitbursar.com/releases/.fgfs
or flightgear
.)<your chosen directory>/data
./Applications
folder. That is it. /Applications/Utilities/Terminal.app
and type the following.$HOME/Documents/Flightgear/<version>
so you can browse the data folder using Finder.fgfs
and can be run without options. If it is 'not found', it is likely not in your path. The location depends on your particular system and choices you made during compile and installation. There is a list of Command Line Parameters which must be used to change many options, like the aircraft you want. The most important:See Volunteer for the main article about this subject. |