Difference between revisions of "Fs2 open on Linux/Optimization"
From FreeSpace Wiki
(Page N) |
m (Fix Title) |
||
Line 1: | Line 1: | ||
{{Page Navigation| | {{Page Navigation| | ||
− | BookName=[[ | + | BookName=[[The fs2_open on Linux Guide]]| |
CurrentPage=Optimization|Optimization| | CurrentPage=Optimization|Optimization| | ||
PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration|Pre-Compile Configuration]]| | PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration|Pre-Compile Configuration]]| |
Revision as of 22:52, 3 September 2007
« Pre-Compile Configuration | The fs2_open on Linux Guide Optimization |
Compiling » |
Warning: If you compile a debug build, don't use the -fomit-frame-pointer and -fno-ident compiler flags, as it will make debugging impossible.
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.
Optimizing fs2_open might have little or no effect, or improve performance greatly, I honestly have no clue.
You can specify your compiler flags with the configure script, se below.
$ ./configure CFLAGS="<your desired flags>"
If you got a i686 and want to play it safe, a good set of CFLAGS would be
$ ./configure CFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer -fno-ident" \ CXXFLAGS="$CFLAGS"
You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links.
http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html
http://gentoo-wiki.com/Safe_Cflags