From e1bb559daa4afca5223a7ad5da4f07043273e07e Mon Sep 17 00:00:00 2001 From: yannk Date: Fri, 17 Dec 2021 23:11:53 +0100 Subject: [PATCH] Instructions how to define local configuration variables for the script --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0ea48df..428b814 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ This repository use [Git LFS](https://git-lfs.github.com/). ### Configuration of the Makefile -The files `global-config.mk` and `local-config.mk` contain configuration informations about paths to sources, executables and to the building destinations. The `global-config.mk` one contains all the variables which can be set and shouldn’t be modified, as it can receive new variables in the future needed for the script to work. Moreover is handled by git for new versions and any changes you make would be erased by new pull of the script. If you want to specify a dedicated value to any variable, you should copy its line definition to the `local-config.mk` file, as it has been done for the preview build folder as example. Like this, you will keep your local configuration files in the future with new versions of the script. +The files `global-config.mk` contain configuration informations about paths to sources, executables and to the building destinations. It details all the variables which can be set but shouldn’t be modified, as it can receive new variables in the future needed for the script to work. Moreover is handled by git for new versions and any changes you make would be erased by new pull of the script. If you want to specify a dedicated value to any variable, you should copy its line definition to a new file inf the same folder, called `local-config.mk`. Like this, you will keep your local configuration files in the future with new versions of the script. Simply write either the absolute or the relative path from your Makefile script situation for any information needed.