The Bitfighter source code
Clone or download
raptor Merge pull request #608 from pterjan/patch-2
Add support for aarch64
Latest commit e60a51c Oct 17, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
alure Explicitly set CMake sub-projects to compile as static libs. This hel… Dec 31, 2015
bitfighter_test Merge branch 'bitfighter-019x'. Also replace other boost::shared_ptr … Mar 5, 2018
boost/boost Fix compile on vc++ 2013 Oct 18, 2013
build Merge remote-tracking branch 'origin/bitfighter-019x' Jun 2, 2018
clipper Explicitly set CMake sub-projects to compile as static libs. This hel… Mar 11, 2017
cmake Merge remote-tracking branch 'origin/bitfighter-019x' Jun 2, 2018
doc Add some documentation Mar 12, 2017
gtest CR/LF -> LF Nov 21, 2013
lib Merge remote-tracking branch 'origin/bitfighter-019x' Sep 16, 2018
libsdl/SDL2 Merge remote-tracking branch 'origin/bitfighter-019x' Sep 16, 2018
lua Merge remote-tracking branch 'origin/bitfighter-019x' Mar 22, 2018
master Merge remote-tracking branch 'origin/bitfighter-019x' Sep 16, 2018
mysql++ OSX can use CMake to compile now. This is still primitive and doesn't… May 27, 2013
nanovg Add comments from the header Feb 11, 2017
notifier Remove trailing spaces Apr 24, 2016
other Move dirent.h into its own directory so as to not conflict with addin… May 12, 2013
packaging/linux Install manpage in man6 which is games-specific Mar 11, 2017
poly2tri Fix warnings for travis build Apr 21, 2017
recast Fix warnings for travis build Apr 21, 2017
resource Add an example that would have been useful today May 1, 2017
sqlite Upgrade sqlite Oct 3, 2016
tnl Merge pull request #608 from pterjan/patch-2 Oct 17, 2018
tnlping Fix windows compiling Jun 25, 2014
tomcrypt Fix tomcrypt build May 28, 2017
updater Integrate our Windows updater (based on GUP) into CMake: Oct 20, 2014
zap Merge remote-tracking branch 'origin/bitfighter-019x' Sep 16, 2018
.gitignore Add .gitignore to 019f branch Mar 11, 2017
.hgeol Line endings Oct 20, 2013
.travis.yml Copy travis files into branch Apr 24, 2017
CMakeLists.txt Cleaning: Finish removing support for GLES1 May 7, 2018
COPYING.txt massive copyright/licensing changes. also removed some cruft from the… Nov 7, 2013
LICENSE.txt Futureproof this baby! Mar 11, 2017
README.txt Integrate testing improvements from oskopek. Thanks!! Jan 21, 2014
luadoc.pl Whitespace May 12, 2016
travis-install-dependencies.sh Copy travis files into branch Apr 24, 2017

README.txt

Bitfighter README

   Many resources are found at:

    http://bitfighter.org/wiki/index.php?title=Main_Page

   Most is still valid...   ;-)

1) DEPENDENCIES

   Bitfighter has several common, open source dependencies:
      * SDL
      * zlib
      * libpng
      * openal
      * libvorbis
      * libspeex
      * libmodplug

   These dependencies are provided for you on Windows and OSX.

   On Linux, you must install them using your distribution's preferred method.

      
2) COMPILING

   The CMake build system is used for compiling on Windows and Linux.  You
   will need to download and install CMake for these platforms.  
   
   On OSX, there is an Xcode project available.

 a) Linux

   You will need the development headers of the above dependencies installed 
   as well as the following software to compile:
      * cmake
      * make
      * gcc / g++

   Open a terminal and change to the 'build' directory within the extracted
   bitfighter sources.  Then run the following commands:

   1) cmake ..
   2) make

   To set up a debugging build do:  cmake -DCMAKE_BUILD_TYPE=Debug ..
   
   To build a dedicated server run 'make bitfighterd'.

   To build tests do: 'make test'. It will create a binary in 'exe/' called 'test'.
   Make sure to copy the resources over to 'exe/', as specified in step 3a), below.

 b) Windows

   Bitfighter can be built with at least the following build systems:
      * Visual Studio C++ IDE 
      * MingW/MSYS

   To generate the proper project files with CMake, go into the 'build' directory
   and type:
      * cmake -G "Visual Studio 10" ..
    OR
      * cmake -G "MSYS Makefiles" ..
      
   To see a list of generators for CMake, see here:
   
    http://www.cmake.org/cmake/help/v2.8.11/cmake.html#section_Generators
    
   Different versions of Visual Studio are known to work, but you need to use the
   correct generator with CMake.
   
   
   Microsoft Visual Studio:
   
   Start Visual C++.  Select Open Project, then navigate to the 'build' folder, 
   and open the bitfighter solution file.

   Right-click on the 'bitfighter' target and select 'build' to compile the game.  This 
   will take a few minutes the first time.

   To run:

   Click Debug > Start Debugging (or press F5) to run the game.

   
   MinGW / MSYS

   After generating the "MSYS Makefiles".  All you have to do is run 'make' to compile


 d) MacOS X (10.4 - 10.7)

   Bitfighter is built with the Xcode IDE.  The Xcode project is found in the directory:

    build/osx/xcode

   To compile, select 'Release' mode and build the Bitfighter target


3) INSTALLATION AND PACKAGING

 a) Linux

   There is no 'make install'.

   After running 'make', the bitfighter executable is put into the directory
   'exe/'.  Copy everything from the 'resources/' directory into the 'exe/'
   directory, keeping the folders intact (like sfx, scripts, etc.)

   Bitfighter can now be run from the 'exe/' folder.

   For distribution packaging, Bitfighter is built for a few distributions
   using the Open Build Service at:

    https://build.opensuse.org/package/show?package=bitfighter&project=games


 b) Windows

   An NSIS build script is found in the following directory:

    build/windows/installer

   This will build a self-extracting installer for Bitfighter.  You will need to 
   build in 'Release' mode as the installer is looking for an executable named 
   'bitfighter.exe'


 c) MacOS X

   Run the target called "Create Bitfighter Game Release" to build a 
   distributable DMG.


4) CRASHES & PROBLEMS

   If you are building off of 'tip' then expect crashes and problems.
   Please don't report them via Google Code; instead join the IRC channel
   #bitfighter on freenode to ask a developer about it - we probably are
   already aware.

   If you are building off of a release version, please make sure you can
   consistently reproduce the problem, then post it, with the steps to
   reproduce at:

    http://code.google.com/p/bitfighter/issues/list

   For feature requests or similar, please post in the forums at:

    http://bitfighter.org/forums/viewforum.php?f=4


5) COMPATIBILITY

   TODO


6) OTHER NOTES

   Come join us in the forums at:

    http://bitfighter.org/forums/

   Enjoy Bitfighter!