Difference between revisions of "Fs2 open on Linux/Optimization"
From FreeSpace Wiki
m (Fixage) |
m |
||
Line 15: | Line 15: | ||
http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br> | http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br> | ||
http://gentoo-wiki.com/Safe_Cflags | http://gentoo-wiki.com/Safe_Cflags | ||
+ | |||
+ | [[Category:FreeSpace Open on Linux|Optimization]] |
Revision as of 18:21, 24 September 2008
« 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