Skip to content

For developers

Timi007 edited this page Jul 21, 2019 · 17 revisions

Coding guidelines

As you know, we all have our own coding styles and guidelines which apparently makes the code only readable for ourselves, if at all. To prevent this issue, and make our lives easier when working on a bigger project together, we must set coding guidelines. And what role model is better than ACE3 or CBA itself? So therefore we're choosing the ACE3 coding guidelines as our standard. Please read and follow the coding guildlines when making a PR.

Installation

This page describes how you can setup your development environment for Metis Marker, allowing you to properly build the Metis (mts) Marker mod and utilize file patching.

1. Requirements

  • Arma 3
  • A proper installation of the Arma 3 Tools (available on Steam)
  • A properly setup P-drive
  • Run Arma 3 and Arma 3 Tools directly from steam once to install registry entries (and again after every update)
  • Python 3.x
  • Mikero Tools: DePbo, DeRap, DeOgg, Rapify, MakePbo, PboProject >=1.70
  • *.hpp removed from PboProject's "Exclude From Pbo" list
  • Python, Mikero Tools and Git in PATH environment variable
  • CBA mod (release or development version)

2. Why so complicated?

Metis Marker uses macros to simplify things and give the developer access to a better debug process, which requires a stricter build environment. Additionally, Mikero’s Tools are stricter and report more errors than AddonBuilder does. The structure of this development environment also allows for file patching, which is very useful for debugging.

Not offering .exes for the Python scripts we use, allows us to make easy changes without the hassle of compiling self-extracting .exes all the time.

3. Getting Source Code

To actually get the Metis Marker source code on your machine, it is recommended that you use Git. Tutorials for this are all around the web, and it allows you to track your changes and easily update your local copy.

If you just want to create a quick and dirty build, you can also directly download the source code using the "Download ZIP" button on the front page of the Github repo.

4. Setup and Building

4.1 Initial Setup

Navigate to tools folder in command line.

cd "[location of the Metis Marker project]\tools"

Execute setup.py to create symbolic links to P-drive and Arma 3 directory required for building.

You can create the required links manually, should the script fail. First, create z folders both in your Arma 3 directory and on your P-drive. Then run the following commands as admin, replacing the text in brackets with the appropriate paths:

mklink /J "[Arma 3 installation folder]\z\mts" "[location of the Metis Marker project]"
mklink /J "P:\z\mts" "[location of the Metis Marker project]"

Then, copy the cba folder from the tools folder to P:\x\cba. Create the x folder if needed. That folder contains the parts of the CBA source code that are required for the macros to work.

4.2 Creating a Test Build

To create a development build of Metis Marker to test changes or to debug something, run the build.py file in the tools folder. This will populate the addons folder with binarized PBOs. These PBOs however still point to the source files in their respective folders, which allows you to use file patching. This also means that you cannot distribute this build to others.

To start the game using this build, you can use the following modline:

-mod=@CBA_A3;z\mts

4.3 Creating a Release Build

To create a complete build of Metis Marker 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 <other-increment-args> force checkexternal release in the tools folder, replacing <other-increment-args> 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)
  • increment_minor - increments minor version number and resets patch version number to 0 (ignored with increment_major)
  • increment_major - increments major version number and resets minor and patch version numbers to 0
  • force - force rebuild all PBOs, even those already present in the release directory (combined with compile it will also rebuild all extensions)
  • checkexternal - check external references (incompatible only with <component1> <component2> and force <component1> <component2>)
  • release - create release packages/archives
  • <component1> <component2> - build only specified component(s) (incompatible with release)
  • force <component1> <component2> - force rebuild specified component(s) (incompatible with release)

7. File Patching

File Patching allows you to change the files in an addon while the game is running, requiring only a restart of the mission. This makes it great for debugging, as it cuts down the time required between tests. Note that this only works with PBOs created using MakePBO, which build.py uses.

To run Arma 3 with file patching add the -filePatching startup parameter (since Arma 3 v1.50, file patching is disabled by default).

7.1 Disabling CBA Function Caching

By default CBA caches a compiled version of functions to reduce mission load times. This interferes with file patching. There are three ways to disable function caching:

  • Load cba_cache_disable.pbo (included in CBA's optional folder - simply move it to addons folder for the time being)
  • Add the following to your test missions description.ext:
class CfgSettings {
    class CBA {
        class Caching {
            compile = 0;
            xeh = 0;
            functions = 0;
        };
    };
};
  • To only disable caching for a single module, hence greatly improving mission restart time, add the following line to the script_component.hpp file of said module (prepared in each Metis Marker component, simply uncomment):
#define DISABLE_COMPILE_CACHE

All functions in module with DISABLE_COMPILE_CACHE line can be recompiled without mission restart with [] call mts_PREP_RECOMPILE; command. You can add a addAction/keybind/pfeh with this code and use it for fast recompiling.

7.2 Restrictions

Files must exist in the built PBOs for file patching to work. If you create a new file you must rebuild the PBO or Arma will not find it in your file paths.

Configs are not patched during run time, only at load time. You do not have to rebuild a PBO to make config changes, just restart Arma. You can get around this though if you are on the dev branch of Arma 3 and running the diagnostic exe. That includes diag_mergeConfigFile which takes a full system path (as in diag_mergeConfigFile ["p:\z\mts\addons\my_module\config.cpp"]) and allows you to selectively reload config files.

If you need to add/remove files, then you'll need to run build.py again while the game is not running. That is all that is required to add new files for further use in testing.

Steps before release:

  1. Merge all wanted Pull-Requests into Master branch
  2. Merge Master branch into Release branch
  3. Commit/bump up version number in Release branch
  4. Build Mod (look up I.)
  5. Cherry-pick commit (3.) to Master branch
  6. Push your local Master and Release branch
  7. Create Release based on Release branch
    1. Titel: Version 1.x.x
    2. Tag: v1.x.x.buildDate

I. For building the mod:
python make.py version force checkexternal release

Clone this wiki locally
You can’t perform that action at this time.