Skip to content

Building Process

Jump to bottom
neitsa edited this page Dec 18, 2016 · 3 revisions

This page shows how to build the RemoteTech-Complete package.

Preparing the subtrees

Note: This work is done on the other RemoteTech repositories.

  1. Publish all necessary feature/ branches (merge all desired feature/ branches onto develop) on the subtree repositories.
  2. Start a git flow release
  3. Test your subtree and apply correction(s) if needed in the release/ branch
  4. When the release/ branch is deemed correct, publish the release.

Building RemoteTech-Complete

On the RemoteTech-Complete repository.

  1. Update all subtrees with the update_subtrees.sh script (or manually using git subtree pull ...)
  2. Start and publish the git flow release
  3. Use the Continuous Integration bot to build the master branch

Continuous Integration Builder

We use appveyor continuous integration builder to build RemoteTech as it allows us to use the latest Visual Studio release.

Appveyor use the yaml (appveyor.yml) file at the root of the cloned repository. A complete documentation on how to write such a configuration file for the builder is available here.

Note that as we are using the git flow branching model we use a conditional build configuration.

Things to take into account

  • To build RemoteTech the CI Bot needs the KSP and unity DLLs: they must be available somewhere on the Internet.

The KSP and Unity 3D assemblies must be put in a folder named KSP_Assemblies in the RemoteTech-Complete/src folder, right next to the other subtrees:

Neitsa@Falcon /RemoteTech/RemoteTech-Complete/src
$ tree -L 2 -d
.
├── KSP_Assemblies
├── RemoteTech-Antennas
│   └── Parts
├── RemoteTech-Common
│   └── src
├── RemoteTech-Delay
│   └── src
└── RemoteTech-Transmitter
    └── src
Clone this wiki locally