Difference between revisions of "Fs2 open on Linux/Compiling"

From FreeSpace Wiki
Jump to: navigation, search
m
 
Line 10: Line 10:
 
Sit back and enjoy gcc work its magic.<br>
 
Sit back and enjoy gcc work its magic.<br>
 
You will find the binary executable in <i>code/</i> as either fs2_open_r if you built a release build or fs2_open_d if you built a debug build.
 
You will find the binary executable in <i>code/</i> as either fs2_open_r if you built a release build or fs2_open_d if you built a debug build.
 +
 +
NOTE: in 3.6.15 and higher, quiet compiles are turned on by default.  To get a verbose compile:
 +
$ V=1 make
 +
Also, the binary executable in <i>code/</i> is now called fs2_open_3.6.15 and fs2_open_3.6.15_DEBUG
  
 
[[Category:FreeSpace Open on Linux|Compiling]]
 
[[Category:FreeSpace Open on Linux|Compiling]]

Latest revision as of 09:21, 31 December 2012

« Optimization The fs2_open on Linux Guide
Compiling
Compile Script »

Note: This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.

Run from within your fs2_open directory:

$ make

Sit back and enjoy gcc work its magic.
You will find the binary executable in code/ as either fs2_open_r if you built a release build or fs2_open_d if you built a debug build.

NOTE: in 3.6.15 and higher, quiet compiles are turned on by default. To get a verbose compile:

$ V=1 make

Also, the binary executable in code/ is now called fs2_open_3.6.15 and fs2_open_3.6.15_DEBUG