forked from endless-sky/endless-sky
-
Notifications
You must be signed in to change notification settings - Fork 0
/
readme-developer.txt
102 lines (58 loc) · 3.77 KB
/
readme-developer.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
Build instructions:
Linux:
Use your favorite package manager to install the following (version numbers may vary depending on your distribution):
DEB-based distros:
g++ \
scons \
libsdl2-dev \
libpng12-dev \
libjpeg-turbo8-dev \
libgl1-mesa-dev \
libglew-dev \
libopenal-dev \
libmad0-dev
RPM-based distros:
gcc-c++ \
scons \
SDL2-devel \
libpng-devel \
libjpeg-turbo-devel \
mesa-libGL-devel \
glew-devel \
openal-soft-devel \
libmad-devel
You can then just navigate to the source code folder in a terminal and type:
$ scons
$ ./endless-sky
The program will run using the "data" and "images" folders that are found in the source code folder itself. For more Linux help, consult the man page (endless-sky.6).
Windows:
The Windows build has been tested on 64-bit Windows 7, only. You will need the Code::Blocks IDE and g++ 4.8 or higher. Code::Blocks is available here:
http://sourceforge.net/projects/codeblocks/files/Binaries/13.12/Windows/codeblocks-13.12-setup.exe/download
You can install g++ separately through mingw-w64:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.5/threads-posix/seh/
*** Be sure to install the "pthread" version of MinGW. The "win32-thread" one does not come with support for C++11 threading. If you are using 32-bit Windows, install the compiler for "dwarf" exceptions, not "sjlj." ***
If you are on 64-bit Windows, a full set of development libraries are available here:
http://endless-sky.github.io/win64-dev.zip
If you don't want to have to edit the paths in the Code::Blocks file, unpack the "dev64" folder directly into C:\.
If you are using 32-bit Windows, a full set of development libraries are available here:
http://endless-sky.github.io/win32-dev.zip
You will probably need to adjust the paths to your compiler binaries, and you should also switch to the "Win32" build instead of the "Debug" or "Release" build.
You will also need libmingw32.a and libopengl32.a. Those should be included in the MinGW g++ install. If they are not in C:\Program Files\mingw64\x86_64-w64-mingw32\lib\ you will have to adjust the paths in the Code::Blocks file.
Mac OS X:
To build Endless Sky you probably want the latest XCode version (I used 5.1.1). You also need to install four libraries:
libpng
http://sourceforge.net/projects/libpng/files/libpng14/
Get version 1.4.13. (The version number doesn't seem to match -- XCode links to libpng14.14.dylib -- but the file name will be right).
On my system, it was installed with the name libpng14.14..dylib (extra ".") and I had to rename it and fix the symlinks.
libturbojpeg
http://www.libjpeg-turbo.org/Documentation/OfficialBinaries
libmad
https://sourceforge.net/projects/mad/files/libmad/0.15.1b/
To get it to build on Mac OS X, you may have to edit the configure script to not default to "i486" for x86 architectures. On my version of OS X gcc is also just an alias for clang, so I also had to edit the Makefile and strip out some optimization flags that the configure script filled in that only work for gcc.
SDL2
Just downloading the SDL binary won't work, because XCode 5 checks that the framework is signed, and it isn't. Instead, build it from source:
hg clone https://hg.libsdl.org/SDL; open SDL/Xcode/SDL/SDL.xcodeproj
Build the framework, then copy it into /Library/Frameworks. When I did this, for some reason it built to some obscure directory that I had to look up in the logs.
Hopefully these will all install to the locations referenced in the project file; if not you can correct the paths.
Library paths
To create a Mac OS X binary that will work on systems other than your own, you may also need to use install_name_tool to modify the libraries so that their location is relative to the @rpath.