4,400
edits
CodeBlocks IDE: Difference between revisions
Jump to navigation
Jump to search
m
Bot: Automated text replacement (-CVS +Git)
m (stub) |
m (Bot: Automated text replacement (-CVS +Git)) |
||
| Line 3: | Line 3: | ||
http://www.CodeBlocks.org - Free open source cross platform IDE, supporting multiple differentcompiler backends | http://www.CodeBlocks.org - Free open source cross platform IDE, supporting multiple differentcompiler backends | ||
Using the free CodeBlocks IDE to compile FlightGear and its dependencies is probably be one of the easiest ways for Windows users (and non-developers) to benefit from the latest bleeding edge | Using the free CodeBlocks IDE to compile FlightGear and its dependencies is probably be one of the easiest ways for Windows users (and non-developers) to benefit from the latest bleeding edge Git version of FlightGear. This document will detail the steps that are required to compile FlightGear from source under Win32 by using gcc (non-cygwin). | ||
1. download the complete IDE, including the mingw-gcc compiler, approx. 13 MB | 1. download the complete IDE, including the mingw-gcc compiler, approx. 13 MB | ||
| Line 23: | Line 23: | ||
You will want to follow the following steps in order to get a working FlightGear version, built from source: | You will want to follow the following steps in order to get a working FlightGear version, built from source: | ||
1) decide whether you want to compile a release version or a | 1) decide whether you want to compile a release version or a Git version. | ||
Depending on whether you want to build FlightGear based on a release or on a | Depending on whether you want to build FlightGear based on a release or on a Git version, the ways to obtain the source code differ, because you will usually either want to download a tarball (compressed archive) of the source code or alternatively check out a particular version of FlightGear's Git version by using a Git client ([[command line]] or GUI client). | ||
RELEASE: | RELEASE: | ||
| Line 32: | Line 32: | ||
TODO: add links | TODO: add links | ||
Git: | |||
in order to compile the latest FlightGear | in order to compile the latest FlightGear Git it is usually required to also make sure that FlightGear's dependencies are not only up to date but often also from Git/HEAD. However, if you want to compile and older Git version, you will also want to make sure that this version's dependencies are met, which may require to downgrade libraries. | ||
TODO: add links, add links to | TODO: add links, add links to Git instructions | ||
FlightGear currently has the following external dependencies: | FlightGear currently has the following external dependencies: | ||
| Line 44: | Line 44: | ||
TODO: links | TODO: links | ||
The latest | The latest Git source code for each dependency is available via: | ||
TODO: links | TODO: links | ||
| Line 57: | Line 57: | ||
to be continued ... | to be continued ... | ||
Either as tarball or from | Either as tarball or from Git | ||
[[Category:Software]] | [[Category:Software]] | ||