From f2e10072953878c458b2e01b4840a138f92033d5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Przemys=C5=82aw=20Sztoch?= Date: Sun, 7 Jul 2019 17:01:29 +0200 Subject: [PATCH] Update Developer-Guide_Build-Preparation.md Base and descendant configuration --- docs/Developer-Guide_Build-Preparation.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/Developer-Guide_Build-Preparation.md b/docs/Developer-Guide_Build-Preparation.md index c4b91b59..46ea6a04 100644 --- a/docs/Developer-Guide_Build-Preparation.md +++ b/docs/Developer-Guide_Build-Preparation.md @@ -31,7 +31,7 @@ Make sure that full path to the build script does not contain spaces. # Providing build configuration -After the first run of `compile.sh` a new configuration file `config-default.conf` will be created. +After the first run of `compile.sh` a new configuration file `config-example.conf` and symlink `config-default.conf` will be created. You may edit it to your needs or create different configuration files using it as a template. Alternatively you can supply options as command line parameters to compile.sh. @@ -41,6 +41,16 @@ Example: Note: Option `BUILD_ALL` cannot be set to "yes" via command line parameter. +## Base and descendant configuration + +You can create one base configuration (`config-base.conf`) and use this in descendant config (`config-dev.conf`). Three parameters (BRANCH, RELEASE, COMPRESS_OUTPUTIMAGE) will be overwritten. + + . ./config-base.conf + + BRANCH="dev" + RELEASE="buster" + COMPRESS_OUTPUTIMAGE="sha,gz" + # Using our automated build system If you don't own the proper equipment to build images on your own, you can make use of the automated build system.