From cda0f1d78e5770ff85af35aac2b005f846ba9d5d Mon Sep 17 00:00:00 2001 From: Jens J Date: Sat, 24 Jun 2023 13:03:12 -0500 Subject: [PATCH] more detail about build configs --- docs/Developer-Guide_Build-Preparation.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/Developer-Guide_Build-Preparation.md b/docs/Developer-Guide_Build-Preparation.md index 00e9967d..4e1a7a4d 100644 --- a/docs/Developer-Guide_Build-Preparation.md +++ b/docs/Developer-Guide_Build-Preparation.md @@ -42,8 +42,9 @@ 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-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. +After the first run of `compile.sh` a new configuration file `config-example.conf` and symlink `config-default.conf` will be created in `userpatches`. +You may edit it to your needs or create different configuration files using it as a template. To start a build with a specific configuration file, e.g. for `config-foo.conf` + ./compile.sh foo Alternatively you can supply options as command line parameters to compile.sh. Example: