23
edits
(→Compiling: Out-of-source explanation and link to cmake wiki.) |
(→Compiling: More CMake background) |
||
| Line 1: | Line 1: | ||
== Compiling == | == Compiling == | ||
=== CMake === | |||
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation. | Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation. | ||
| Line 5: | Line 7: | ||
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>. | CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>. | ||
=== Example "out-of-source" build with CMake === | ==== Example "out-of-source" build with CMake ==== | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
| Line 12: | Line 14: | ||
build.simgear $ cmake ../simgear | build.simgear $ cmake ../simgear | ||
</syntaxhighlight> | </syntaxhighlight> | ||
==== <tt>ccmake</tt> ==== | |||
CMake build configuration files (<tt>CMakeCache.txt</tt>) are designed to be edited and generated. A GUI has been baked in since the beginning of the CMake project, which allows editing of configuration settings (like <tt>configure</tt> parameters). | |||
For Ubuntu, the package <tt>cmake-curses-gui</tt> needs to be install to use the <tt>ccmake</tt> GUI. | |||
==== Installation with CMake ==== | |||
After CMake has run, you can <code>make && make install</code>. | After CMake has run, you can <code>make && make install</code>. | ||
edits