flewkey/cuberite-2a
1
0
Fork 0
Code Releases Activity

Improved compiling file.

Browse Source
This commit is contained in:
Alexander Harkness 2015-11-15 12:22:23 +00:00
parent 64f9974e89
commit 8969931e6f
1 changed files with 53 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

83
COMPILING.md
View File

@ -1,30 +1,43 @@
# COMPILING # COMPILING
=========
To compile Cuberite from source, you need CMake and make, as well as a C compiler, C++ compiler and linker. To contribute code, you also need a Git client. To compile Cuberite from source, you need the following set of software:
## Windows ## * CMake
* Platform-specific make tool (windows would be MSVC, linux/osx GNU make, etc.)
* C compiler
* modern C++ compiler and linker
To contribute code, you also need a Git client.
Windows
-------
We use Microsoft Visual Studio for Windows compilation. It is possible to use other toolchains, but we don't test against them and they aren't supported. Visual Studio 2013 Express for Desktop is being actively used for development.
We use Microsoft Visual Studio for Windows compilation. It is possible to use other toolchains, but it isn't tested nor supported. Visual Studio versions 2013 Express for Desktop is being actively used for development.
You can find download links for VS2013 Express here: http://go.microsoft.com/?linkid=9832280 You can find download links for VS2013 Express here: http://go.microsoft.com/?linkid=9832280
Next, you need to download and install CMake. Download from here: http://cmake.org/cmake/resources/software.html . You should download a full installation package, so that the installer will set everything up for you (especially the paths). Next, you need to download and install CMake. Download from here: http://cmake.org/cmake/resources/software.html . You should download a full installation package, so that the installer will set everything up for you (especially the paths).
To contribute your changes to the sources back to the repository, you need a Git client. Options are: To contribute your changes to the source back to the repository, you need a Git client. Options are:
- MsysGit: http://msysgit.github.io/
- GitHub windows client: http://windows.github.com/ * MsysGit: http://msysgit.github.io/
- TortoiseGit: http://code.google.com/p/tortoisegit/ * GitHub windows client: http://windows.github.com/
* TortoiseGit: http://code.google.com/p/tortoisegit/
Alternatively, if you want only to compile the source, without contributing, you can [download the sources in a ZIP file directly from GitHub](https://github.com/cuberite/cuberite/archive/master.zip).
If you're using Git to get the source, use the following set of commands to set up the local workspace correctly:
Alternatively, if you want only to compile the source, without contributing, you can download the sources in a ZIP file directly from GitHub: https://github.com/cuberite/cuberite/archive/master.zip
If you're using Git to get the sources, use the following set of commands to set up the local workspace correctly:
``` ```
git clone --recursive https://github.com/cuberite/cuberite.git git clone --recursive https://github.com/cuberite/cuberite.git
``` ```
Now that you have the sources, it's time to prepare the project files for your favorite compiler. Open a command window in the folder with the sources and type in `cmake .` . This will run CMake, it will auto-detect your Visual Studio version and produce the appropriate project and solution files. Now that you have the source, it's time to prepare the project files for your favorite compiler. Open a command window in the folder with the source and type in `cmake .` . This will run CMake, it will auto-detect your Visual Studio version and produce the appropriate project and solution files.
Finally, open the newly created file, `Cuberite.sln`, in your Visual Studio. Finally, open the newly created file, `Cuberite.sln`, in your Visual Studio.
If you want to run Cuberite from within the IDE, you need to first make sure that it will be run with the correct home folder. Normally this happens automatically, but for some Visual Studio versions the process doesn't stick. Right-click on the Cuberite project in the Solution Explorer tool window, and select Properties. In the dialog, navigate to Configuration properties -> Debugging in the tree on the left, then make sure the value `Working Directory` is set to `../Server`. If you don't do this, the server won't be able to find crafting recipes, item names or plugins. If you want to run Cuberite from within VS, you need to first make sure that it will be run with the correct home folder. Normally this happens automatically, but for some Visual Studio versions the process doesn't stick. Right-click on the Cuberite project in the Solution Explorer tool window, and select Properties. In the dialog, navigate to Configuration properties -> Debugging in the tree on the left, then make sure the value `Working Directory` is set to `../Server`. If you don't do this, the server won't be able to find crafting recipes, item names or plugins.
### Release configuration ### ### Release configuration ###
@ -32,16 +45,19 @@ To make Visual Studio produce the version with the best performance, you will ne
### Debug configuration ### ### Debug configuration ###
In order to tinker with the code, you'll more than likely need to use the debugging features of the IDE. To make them the easiest to use, you should switch to the Debug configuration - this provides the highest level of information while debugging, for the price of the executable being 2 - 10 times slower. Go to menu Build -> Configuration Manager, and in the opened dialog, change the top left combo box (Active solution configuration) to Debug. Close the dialog and build the solution. The resulting executable is called `Cuberite_debug.exe` in the `Server` folder. In order to tinker with the code, you'll more than likely need to use the debugging features of your IDE. To make them the easiest to use, you should switch to the Debug configuration - this provides the highest level of information while debugging, for the price of the executable being 2 - 10 times slower. Go to menu Build -> Configuration Manager, and in the opened dialog, change the top left combo box (Active solution configuration) to Debug. Close the dialog and build the solution. The resulting executable is called `Cuberite_debug.exe` in the `Server` folder.
OSX
---
## OSX ##
Install git from its [website](http://git-scm.com) or homebrew: `brew install git`. Install git from its [website](http://git-scm.com) or homebrew: `brew install git`.
Install Xcode (commandline tools are recommended) from the App Store or https://developer.apple.com/downloads. Install Xcode (commandline tools are recommended) from the App Store or [the website](https://developer.apple.com/downloads).
Install CMake from its [website](http://cmake.org) or homebrew: `brew install cmake`. Install CMake from its [website](http://cmake.org) or homebrew: `brew install cmake`.
### Getting the sources ### ### Getting the sources ###
``` ```
git clone --recursive https://github.com/cuberite/cuberite.git git clone --recursive https://github.com/cuberite/cuberite.git
``` ```
@ -53,15 +69,18 @@ Follow the instructions at [CMake on Unix-based platforms](#cmake-on-unix-based-
After doing so, run the command `xcodebuild lib/polarssl/POLARSSL.xcodeproj` in the build directory, in order to build polarssl, a library that is required by Cuberite. Lastly, run the command `xcodebuild` to build Cuberite. Optionally, you may open the project files for polarssl and then Cuberite in Xcode and build there. After doing so, run the command `xcodebuild lib/polarssl/POLARSSL.xcodeproj` in the build directory, in order to build polarssl, a library that is required by Cuberite. Lastly, run the command `xcodebuild` to build Cuberite. Optionally, you may open the project files for polarssl and then Cuberite in Xcode and build there.
## Linux, FreeBSD etc. ## Linux, FreeBSD etc.
-------------------
Install git, make, cmake and gcc or clang, using your platform's package manager: Install git, make, cmake and clang (or gcc), using your platform's package manager. debian/ubuntu:
```
sudo apt-get install git make cmake gcc g++ ```
``` sudo apt-get install git make cmake clang
(Ensure you have gcc/g++ 4.8 or higher installed to avoid errors during compilation) ```
(Ensure you have a recent version of clang, or gcc/g++ 4.8 or higher installed to avoid errors during compilation)
### Getting the source ###
### Getting the sources ###
``` ```
git clone --recursive https://github.com/cuberite/cuberite.git git clone --recursive https://github.com/cuberite/cuberite.git
``` ```
@ -70,21 +89,24 @@ git clone --recursive https://github.com/cuberite/cuberite.git
Follow the instructions at [CMake on Unix-based platforms](#cmake-on-unix-based-platforms). Follow the instructions at [CMake on Unix-based platforms](#cmake-on-unix-based-platforms).
After doing so, run the command `make` in the build directory, and Cuberite will build. After doing so, run the command `make` in the build directory, and Cuberite will build.
## CMake on Unix-based platforms ### CMake on Unix-based platforms
-----------------------------
### Release Mode ### ### Release Mode ###
Release mode is preferred for almost all cases, it has much better speed and less console spam. However, if you are developing Cuberite actively, debug mode might be better. Release mode is preferred for almost all cases, it has much better speed and less console spam. However, if you are developing Cuberite actively, debug mode might be better.
Assuming you are in the Cuberite folder created in the initial setup step, you need to run these commands: Assuming you are in the Cuberite folder created in the initial setup step, you need to run these commands:
``` ```
mkdir Release mkdir Release
cd Release cd Release
cmake -DCMAKE_BUILD_TYPE=RELEASE .. cmake -DCMAKE_BUILD_TYPE=RELEASE ..
``` ```
NOTE: CMake can generate project files for many different programs, such as Xcode, eclipse, and ninja. To use a different generator, first type `cmake --help`, and at the end, cmake will output the different generators that are available. To specify one, add `-G` followed by the name of the generator, in the `cmake` command. Note that the name is case-sensitive.
NOTE: CMake can generate project files for many different programs, such as Xcode, eclipse, and ninja. To use a different generator, first type `cmake --help`, and at the end, cmake will output the different generators that are available. To specify one, add `-G` followed by the name of the generator, in the `cmake` command. Note that the name is case-sensitive.
The executable will be built in the `cuberite/Server` folder and will be named `Cuberite`. The executable will be built in the `cuberite/Server` folder and will be named `Cuberite`.
@ -93,30 +115,31 @@ The executable will be built in the `cuberite/Server` folder and will be named `
Debug mode is useful if you want more debugging information about Cuberite while it's running or if you want to use a debugger like GDB to debug issues and crashes. Debug mode is useful if you want more debugging information about Cuberite while it's running or if you want to use a debugger like GDB to debug issues and crashes.
Assuming you are in the Cuberite folder created in the Getting the sources step, you need to run these commands: Assuming you are in the Cuberite folder created in the Getting the sources step, you need to run these commands:
``` ```
mkdir Debug mkdir Debug
cd Debug cd Debug
cmake -DCMAKE_BUILD_TYPE=DEBUG .. cmake -DCMAKE_BUILD_TYPE=DEBUG ..
``` ```
NOTE: CMake can generate project files for many different programs, such as Xcode, eclipse, and ninja. To use a different generator, first type `cmake --help`, and at the end, cmake will output the different generators that are available. To specify one, add `-G` followed by the name of the generator, in the `cmake` command. Note that the name is case-sensitive.
NOTE: CMake can generate project files for many different programs, such as Xcode, eclipse, and ninja. To use a different generator, first type `cmake --help`, and at the end, cmake will output the different generators that are available. To specify one, add `-G` followed by the name of the generator, in the `cmake` command. Note that the name is case-sensitive.
The executable will be built in the `cuberite/Server` folder and will be named `Cuberite_debug`. The executable will be built in the `cuberite/Server` folder and will be named `Cuberite_debug`.
### 32 Bit Mode switch ### ### 32 Bit Mode switch ###
This is useful if you want to compile Cuberite on an x64 (64-bit Intel) machine but want to use on an x86 (32-bit Intel) machine. This switch can be used with debug or release mode. Simply add: This is useful if you want to compile Cuberite on an x64 (64-bit Intel) machine but want to use on an x86 (32-bit Intel) machine. This switch can be used with debug or release mode. Simply add:
-DFORCE_32=1 -DFORCE_32=1
to your cmake command and 32 bit will be forced. to your cmake command and 32 bit will be forced.
### Compiling for another computer ### ### Compiling for another computer ###
When cross-compiling for another computer it is important to set cross compiling mode. This tells the compiler not to optimise for your machine. This switch can be used with debug or release mode. To enable, simply add: When cross-compiling for another computer it is important to set cross compiling mode. This tells the compiler not to optimise for your machine. This switch can be used with debug or release mode. To enable, simply add:
-DCROSSCOMPILE=1 -DCROSSCOMPILE=1
to your cmake command. to your cmake command.
Note that cross-compilation is probably broken at this moment, since the build requires running an executable that it has built, as part of the build process. Note that real cross-compilation is hard at this moment, because an executable generated during the build process is required for later stages, so if your computer cannot run executables it generates the build will not work.