Editing MG/Mac Compiling
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
This page explains how to compile [[MegaGlest]] on a Mac computer. | This page explains how to compile [[MegaGlest]] on a Mac computer. | ||
| − | |||
==Prerequisites== | ==Prerequisites== | ||
| − | * XCode | + | * [http://developer.apple.com/technologies/xcode.html XCode] |
| − | * Various 3rd party build dependencies | + | * [http://www.cmake.org/cmake/resources/software.html CMake] |
| − | + | * Various 3rd party build dependencies | |
| + | * GCC (Optional, but may be needed to achieve stable network compatibility for multiplayer games) | ||
=== Dependencies === | === Dependencies === | ||
Dependencies can be installed in two ways: | Dependencies can be installed in two ways: | ||
| − | + | * Retrieve the build dependencies / 3rd party libraries and extract the contents of the archive in your library directory ~/Library/Frameworks | |
| + | or | ||
* Install them using a 3rd party package manager like [https://www.macports.org/ MacPorts] or [http://www.finkproject.org/ Fink]. | * Install them using a 3rd party package manager like [https://www.macports.org/ MacPorts] or [http://www.finkproject.org/ Fink]. | ||
| − | In this example | + | In this example I show how to install the packages with MacPorts which will handle the install of dependencies, and there is a lot of them. Full dependency lists are available on [[MG/Linux Compiling|Linux Compiling]] or [[MG/FreeBSD Compiling|FreeBSD Compiling]] if you would like to install them manually. |
| − | sudo port install git | + | sudo port install git cmake VLC-devel fribidi ftgl glew wxWidgets-2.8 wxgtk-2.8 |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Configuring Environment === | === Configuring Environment === | ||
| − | Once wxwidgets is installed you will need to ensure '''wx-config''' is in your path | + | Once wxwidgets is installed you will need to ensure '''wx-config''' is in your path. Add the following fragment to ''~/.profile'' or the configuration file appropriate to your shell. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
# Add wx-config to path for cmake | # Add wx-config to path for cmake | ||
export PATH=$PATH:/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxGTK/2.8/bin/ | export PATH=$PATH:/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxGTK/2.8/bin/ | ||
Once that has been added you will need to source the configuration file again to pick up the new settings | Once that has been added you will need to source the configuration file again to pick up the new settings | ||
| + | |||
source ~/.profile | source ~/.profile | ||
== Preparing to compile == | == Preparing to compile == | ||
| − | + | However you choose to compile you will need to use [[MG/Getting_The_Code|''Git to check out'']] the MegaGlest source code ready for building. | |
| − | |||
==Compiling== | ==Compiling== | ||
| − | This can be done in two ways: Using an XCode project or GNU Make | + | This can be done in two ways: Using an XCode project or GNU Make |
| − | ( | + | If you change between methods (and if you want to e extra sure your changes are being made between runs) this command will remove previous run/s ouput. |
| − | + | rm -rf Makefile CMakeCache.txt MegaGlest.xcodeproj/ | |
| − | |||
| − | == | + | === XCode project === |
| − | |||
| + | Generate the XCode project (At the moment disabling Map Editor is required for the build to succeed.) | ||
| + | cmake -GXcode -DBUILD_MEGAGLEST_MAP_EDITOR=OFF -DWANT_DEV_OUTPATH=ON | ||
| − | + | Build everything for Release or Debug (This is case sensitive). Depending on the options chosen above you may need to choose a different option here. EG, doing a debug build without DBUILD_MEGAGLEST_MAP_EDITOR=OFF will fail. | |
| − | + | xcodebuild -configuration Release | |
| − | |||
| − | |||
| − | This | + | Generate the installer (This is currently broken!) |
| + | cpack -C CPackConfig.cmake | ||
| − | + | You should have a megaglest-#.dmg file in your current directory. You can install this and play it. | |
| − | + | Alternatively you can choose to run directly without installing , see 'Running the game' below. | |
| + | === GNU Make === | ||
| + | Generate the Makefile, disabling map editor and turn on binary generation. | ||
| + | cmake -G"Unix Makefiles" -DBUILD_MEGAGLEST_MAP_EDITOR=OFF -DWANT_DEV_OUTPATH=ON | ||
| − | + | Build using gnumake | |
| + | gnumake | ||
| − | + | == Running the game == | |
| − | + | Before running make sure you move the megaglest binaries to mk/macosx and copy glest-dev.ini in to the same directory as the binaries. When moving the binaries they wil end up in different locations depending on how they were built - gnumake will put them in data/glest_game while Xcode will put them under a Release or Debug directory depending on the build style selected. | |
| − | + | mv data/glest_game/megaglest* mk/macosx/ | |
| + | cp mk/linux/*.ini mk/macosx/ | ||
| − | + | Run it with | |
| − | + | open -F ./mk/macosx/megaglest | |
| − | |||
| − | - | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==See Also== | ==See Also== | ||
| Line 105: | Line 73: | ||
*[[MG/Windows Compiling|Windows Compiling]] | *[[MG/Windows Compiling|Windows Compiling]] | ||
*[[MG/FreeBSD Compiling|FreeBSD Compiling]] | *[[MG/FreeBSD Compiling|FreeBSD Compiling]] | ||
| − | |||
| − | |||
| − | |||
| − | |||