Prerequisites:
Jun 16, 2007 Compiling Warzone 2100 on Mac OS X Published on June 16, 2007, 8:53 p.m. They have a universal.dmg for Tiger. Which contains a handy-dandy file called COMPILE. I suggest you read it. To start of, I opened a terminal and cd'd into the warzone2100-2.0.6 directory.
- Jun 16, 2007 Here's the list of stuff I had to get/install/compile before I could even start on Warzone 2100: cmake (to compile physfs), physfs, a newer bison, and SDLnet; First I grab cmake 2.4.6. Luckily, they have a universal.dmg for Tiger. Next, I grab the source code for physfs-1.1.1 from their download page. At first I tried compiling the 'Unix Way.
- Building Warzone for macOS Prerequisites: For convenience, you will probably want either Homebrew or Macports installed for setting up certain prerequisites. If you don't have either yet, Homebrew is recommended. MacOS 10.12+ While building may work on prior.
- Welcome Warzone 2100 fans! Files: - warzone2100-3.1.2.exe - The main Windows build warzone2100-3.1.2portable.exe - The portable version of the Windows build (self contained - install it anywhere!) warzone2100-3.1.2-vidsportable.exe - Same as above, plus the videos!
For convenience, you will probably want either Homebrew or Macports installed for setting up certain prerequisites. If you don't have either yet, Homebrew is recommended.
Building on macOS 10.12-10.14 | Building on macOS 10.15+ |
---|---|
Xcode 8 / 9 / 10 | Xcode 11+ |
CMake 3.14.1+ | CMake 3.15+ |
Gettext | Gettext |
Asciidoctor | Asciidoctor |
GCC 7+* |
- macOS 10.12+
- While building may work on prior versions of macOS, it is only tested on macOS 10.12+.
- Xcode 8+ (tested w/: Xcode 8.3 - Xcode 11.x)
- If you do not have Xcode 8.3+ you can get it for free at the Mac App Store or Apple's website.
- CMake 3.14.1+ (required to generate the Xcode project)
- If you do not have CMake 3.14+, you can download the latest stable version for free at CMake.org.
- Gettext (required to compile the translations and language files)
- If you have Homebrew installed, you can use the following command in Terminal:The build scripts work perfectly with the default (keg-only) Homebrew install of gettext.
- If you have Macports installed, you can use the following command in Terminal:
- If you have Homebrew installed, you can use the following command in Terminal:
- Asciidoctor (required to build the documentation / help files)
- If you have Homebrew installed, you can use the following command in Terminal:
- If you have Macports installed, you can use the following command in Terminal:
- Or, via
gem install
:Depending on system configuration,sudo gem install
may be required.
- GCC (*currently required to build vcpkg on macOS < 10.15, and with Xcode < 11)
- If you have Homebrew installed, you can use the following command in Terminal:
Setup & Configuration:
Generating the macOS port's build environment & configuration requires the following steps in Terminal:
1. Create a build directory
The recommended place for the build directory is outside of the Git repo / source code.
For example,
- if you wanted to create a build directory one level up from the Git repo / source code
- and you cloned the Git repo to
~/src/warzone2100
you could use the following commands:
![2100 2100](/uploads/1/2/5/3/125378783/937591339.jpg)
2. Run configure_mac.cmake from the build directory
cd
into the build directory you created in the step above- Run the
configure_mac.cmake
script:Where the../warzone2100/configure_mac.cmake
path should be modified to point toconfigure_mac.cmake
inside the Git repo / source code directory.
The
configure_mac.cmake
script will automatically:- Download + build vcpkg
- Build required dependencies
- Run CMake to generate the Xcode project
Warzone 2100 Mac Dmg File Type
Building:
The macOS port is built using the Xcode project generated by CMake. If following the instructions above, this will be located in your build directory:
<path_to_build_directory>/warzone2100.xcodeproj
To build the game from the command-line:
cd
into your build directory that contains the generatedwarzone2100.xcodeproj
- Run the following command:
You can also simply open the project in Xcode, and build the
warzone2100
scheme. (You may want to tweak it to build in a Release configuration - the default for that scheme in 'Run' mode is Debug, for easier development.)Deployment:
The macOS port produces a 64-bit self-contained application bundle that requires macOS 10.10+* to run.
* See Setup & Configuration for how to set the minimum deployment target.
Additional Information:
The macOS port supports sandboxing, but this requires code-signing to be configured in the Xcode project.(By default, code-signing is disabled in the Xcode project.)
Prerequisites:
For convenience, you will probably want either Homebrew or Macports installed for setting up certain prerequisites. If you don't have either yet, Homebrew is recommended.
Building on macOS 10.12-10.14 | Building on macOS 10.15+ |
---|---|
Xcode 8 / 9 / 10 | Xcode 11+ |
CMake 3.14.1+ | CMake 3.15+ |
Gettext | Gettext |
Asciidoctor | Asciidoctor |
GCC 7+* |
- macOS 10.12+
- While building may work on prior versions of macOS, it is only tested on macOS 10.12+.
- Xcode 8+ (tested w/: Xcode 8.3 - Xcode 11.x)
- If you do not have Xcode 8.3+ you can get it for free at the Mac App Store or Apple's website.
- CMake 3.14.1+ (required to generate the Xcode project)
- If you do not have CMake 3.14+, you can download the latest stable version for free at CMake.org.
- Gettext (required to compile the translations and language files)
- If you have Homebrew installed, you can use the following command in Terminal:The build scripts work perfectly with the default (keg-only) Homebrew install of gettext.
- If you have Macports installed, you can use the following command in Terminal:
- If you have Homebrew installed, you can use the following command in Terminal:
- Asciidoctor (required to build the documentation / help files)
- If you have Homebrew installed, you can use the following command in Terminal:
- If you have Macports installed, you can use the following command in Terminal:
- Or, via
gem install
:Depending on system configuration,sudo gem install
may be required.
- GCC (*currently required to build vcpkg on macOS < 10.15, and with Xcode < 11)
- If you have Homebrew installed, you can use the following command in Terminal:
Setup & Configuration:
Generating the macOS port's build environment & configuration requires the following steps in Terminal:
1. Create a build directory
The recommended place for the build directory is outside of the Git repo / source code.
For example,
- if you wanted to create a build directory one level up from the Git repo / source code
- and you cloned the Git repo to
~/src/warzone2100
you could use the following commands:
2. Run configure_mac.cmake from the build directory
cd
into the build directory you created in the step above- Run the
configure_mac.cmake
script:Where the../warzone2100/configure_mac.cmake
path should be modified to point toconfigure_mac.cmake
inside the Git repo / source code directory.
The
configure_mac.cmake
script will automatically:- Download + build vcpkg
- Build required dependencies
- Run CMake to generate the Xcode project
Building:
The macOS port is built using the Xcode project generated by CMake. If following the instructions above, this will be located in your build directory:
<path_to_build_directory>/warzone2100.xcodeproj
To build the game from the command-line:
cd
into your build directory that contains the generatedwarzone2100.xcodeproj
- Run the following command:
You can also simply open the project in Xcode, and build the
warzone2100
scheme. (You may want to tweak it to build in a Release configuration - the default for that scheme in 'Run' mode is Debug, for easier development.)![Dmg Dmg](/uploads/1/2/5/3/125378783/973535370.jpg)
Deployment:
The macOS port produces a 64-bit self-contained application bundle that requires macOS 10.10+* to run.
* See Setup & Configuration for how to set the minimum deployment target.
Warzone 2100 Mac Dmg File Wiki
Additional Information:
Warzone 2100 Ps1
The macOS port supports sandboxing, but this requires code-signing to be configured in the Xcode project.(By default, code-signing is disabled in the Xcode project.)