From 9e37dc1192c9e4a54953cd126126f98debe4ed2f Mon Sep 17 00:00:00 2001 From: jonpas Date: Tue, 1 Nov 2016 13:50:00 +0100 Subject: [PATCH] Fix make.py wiki lists --- .../wiki/development/setting-up-the-development-environment.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/wiki/development/setting-up-the-development-environment.md b/docs/wiki/development/setting-up-the-development-environment.md index c0333ac590..f2cdfc01ab 100644 --- a/docs/wiki/development/setting-up-the-development-environment.md +++ b/docs/wiki/development/setting-up-the-development-environment.md @@ -72,14 +72,17 @@ To start the game using this build, you can use the following modline: ## 4.3 Creating a Release Build To create a complete build of ACE3 that you can use without the source files you will need to: + - Ensure `.hpp` is **NOT** in pboProject's "Exclude From Pbo" list When the requirements are met: + - Execute `make.py version increment_build force check_external release` in the `tools` folder, replacing `` with the part of version you want to increment (options described below) This will populate the `release` folder with binarized PBOs, compiled extensions, copied extras, bisigns and a bikey. Additionally, an archive file will also be created in the folder. The folder and archive handle like those of any other mod. Different `make.py` command line options include: + - `version` - update version number in all files and leave them in working directory (leaving this out will still update the version in all files present in the `release` folder, but they will be reverted to not disturb the working directory) - `increment_build` - increments _build_ version number - `increment_patch` - increments _patch_ version number (ignored with `increment_minor` or `increment_major`)