6,566
edits
Building using CMake: Difference between revisions
Jump to navigation
Jump to search
Switch to {{flightgear url}} to fix the broken Gitorious link. And usage of {{flightgear clone}} and {{simgear clone}} to abstract the repository cloning.
m (Missing path= parameter name, fixed link) |
(Switch to {{flightgear url}} to fix the broken Gitorious link. And usage of {{flightgear clone}} and {{simgear clone}} to abstract the repository cloning.) |
||
| Line 53: | Line 53: | ||
The easiest solution is to grab the 3rd-party dependencies build from Jenkins: {{Build link|path=job/Mac-3rdparty-deps/lastSuccessfulBuild/artifact/*zip*/archive.zip}}. This will give you a 'dist' directory containing PLIB, Subversion and OpenSceneGraph correctly configured. When configured SimGear and FlightGear, simply use this dist directory as CMAKE_INSTALL_PREFIX, and all the dependencies should be found with no other steps. | The easiest solution is to grab the 3rd-party dependencies build from Jenkins: {{Build link|path=job/Mac-3rdparty-deps/lastSuccessfulBuild/artifact/*zip*/archive.zip}}. This will give you a 'dist' directory containing PLIB, Subversion and OpenSceneGraph correctly configured. When configured SimGear and FlightGear, simply use this dist directory as CMAKE_INSTALL_PREFIX, and all the dependencies should be found with no other steps. | ||
{{#tag:syntaxhighlight| | |||
# make a top-level directory to contain everything | # make a top-level directory to contain everything | ||
mkdir FGFS | mkdir FGFS | ||
| Line 62: | Line 62: | ||
# clone from Git | # clone from Git | ||
{{simgear clone}} | |||
{{flightgear clone}} | |||
mkdir sgbuild | mkdir sgbuild | ||
| Line 75: | Line 75: | ||
cmake ../flightgear -DCMAKE_INSTALL_PREFIX=$PWD/../dist | cmake ../flightgear -DCMAKE_INSTALL_PREFIX=$PWD/../dist | ||
make; make install | make; make install | ||
| lang = "sh" | |||
}} | |||
Note this demonstrates start from a clean setup - after the initial build it's sufficient to simply 'git pull' in the clones repositories, then execute a 'make; make install' in the build directories. You can of course have multiple build directories with different configurations, as described in more detail below. | Note this demonstrates start from a clean setup - after the initial build it's sufficient to simply 'git pull' in the clones repositories, then execute a 'make; make install' in the build directories. You can of course have multiple build directories with different configurations, as described in more detail below. | ||
| Line 186: | Line 187: | ||
* '''-DENABLE_RTI=ON''' (enable [[HLA]] support) | * '''-DENABLE_RTI=ON''' (enable [[HLA]] support) | ||
* '''-DJPEG_FACTORY=ON''' (enable jpeg support) | * '''-DJPEG_FACTORY=ON''' (enable jpeg support) | ||
* '''-DENABLE_FLITE=ON''' (enable FLITE TTS-based ATIS) [http://sourceforge.net/p/flightgear/mailman/message/32265565] [ | * '''-DENABLE_FLITE=ON''' (enable FLITE TTS-based ATIS) [http://sourceforge.net/p/flightgear/mailman/message/32265565] [{{flightgear url|commit=cadb77b18d13bb0d45672ac607801bda222454e9}}] | ||
== XCode == | == XCode == | ||