summaryrefslogtreecommitdiffstats
path: root/INSTALL-MXE.md
diff options
context:
space:
mode:
authorPiotr Dziwinski <piotrdz@gmail.com>2013-11-26 00:42:46 +0100
committerPiotr Dziwinski <piotrdz@gmail.com>2013-11-26 00:42:46 +0100
commitd6eb095f2760eab42e852aceae61289ad7ba36ee (patch)
tree3bf29be57a9c47b0ce7427f3dbb9d58cdd258ee5 /INSTALL-MXE.md
parent881802b050dc9957ce681eafd6e255ddadf3a517 (diff)
parent8c25650ad5e888019f350f099d6755921780c6f1 (diff)
downloadcolobot-d6eb095f2760eab42e852aceae61289ad7ba36ee.tar.gz
colobot-d6eb095f2760eab42e852aceae61289ad7ba36ee.tar.bz2
colobot-d6eb095f2760eab42e852aceae61289ad7ba36ee.zip
Colobot Gold 0.1.2-alpha
Diffstat (limited to 'INSTALL-MXE.md')
-rw-r--r--INSTALL-MXE.md25
1 files changed, 17 insertions, 8 deletions
diff --git a/INSTALL-MXE.md b/INSTALL-MXE.md
index f12ed88..2074de0 100644
--- a/INSTALL-MXE.md
+++ b/INSTALL-MXE.md
@@ -29,7 +29,6 @@ To cross-compile Colobot using MXE:
* check-requirements
* expat
* flac
- * flac
* freetype
* gcc
* gcc-gmp
@@ -55,15 +54,25 @@ To cross-compile Colobot using MXE:
* xz
* zlib
-4. Now `cd` to directory with colobot sources. To cross-compile a CMake project,
- you have to specify a CMake toolchain file. MXE has such file in MXE's directory:
- `usr/i686-pc-mingw32/share/cmake/mxe-conf.cmake`
- Toolchain file is specified thus:`cmake -DCMAKE_TOOLCHAIN_FILE=/path/to/mxe-conf.cmake .`
+4. Now `cd` to directory with colobot sources.
+ It is recommended that you create a separate directory for out-of-source build:
+ `mkdir build-mxe && cd build-mxe`
+
+ In order to cross-compile a CMake project, you have to specify a CMake toolchain file.
+ MXE has such file in MXE's directory: `usr/i686-pc-mingw32/share/cmake/mxe-conf.cmake`
+ So you should use the following cmake command: `cmake -DCMAKE_TOOLCHAIN_FILE=/path/to/mxe-conf.cmake ..`
CMake files in Colobot should detect that MXE is being used and they will
modify flags, paths, etc. as required. You should not run into any problems.
- *Note:* you may also want to use a separate out-of-source build directory for MXE.
-5. `make` should now compile the game with the resulting exe in `bin/colobot.exe`.
+5. `make` should now compile the game with the resulting executable as `colobot.exe`.
The exe is linked against all libraries *statically*, so there are no dependencies
on external DLLs. However, the resulting binary will be huge with all these libraries,
- so you might want to do: `strip bin/colobot.exe`.
+ so you might want to do: `strip colobot.exe`.
+
+6. If you want to create a Colobot installer, you need to additionally build 'nsis'
+ in MXE. Then you can create the NSIS installer that way:
+ `PATH=/path/to/mxe/binaries:$PATH make package`
+ where `/path/to/mxe/binaries` is path to cross-compiled MXE binaries available
+ in MXE's directory under `usr/i686-pc-mingw32/bin`.
+ This will create a versioned colobot-$version.exe installer that will install Colobot
+ in system directories, add a shortcut in the start menu and setup an uninstaller.