From 52e877d0160edbc96bcfcd7d9a4b05db3602963b Mon Sep 17 00:00:00 2001 From: Romain Forlot Date: Sat, 9 Sep 2017 16:07:37 +0200 Subject: Update doc Change-Id: I942267d9673651db6986177e8d47aa0dbc235e3e Signed-off-by: Romain Forlot --- docs/dev_guide/4_advanced_customization.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'docs/dev_guide/4_advanced_customization.md') diff --git a/docs/dev_guide/4_advanced_customization.md b/docs/dev_guide/4_advanced_customization.md index a9974a8..58e6e9a 100644 --- a/docs/dev_guide/4_advanced_customization.md +++ b/docs/dev_guide/4_advanced_customization.md @@ -32,6 +32,7 @@ set(VARIABLE_NAME 'value string random' CACHE STRING 'docstring') ### OS custom cmake files + This is meant to personalize the project depending on the OS your are using. At the end of config.cmake, common.cmake will include lot of cmake file to customize project build depending on your plateform. It will detect your OS @@ -45,7 +46,12 @@ _app-templates/../cmake/_ Those files has to be named use the following scheme _XX-${OSRELEASE}*.cmake_ where _XX_ are numbers, ${OSRELEASE} the **ID_LIKE** or **ID** field from -_/etc/os-release_ file. +_/etc/os-release_ file. You can also define default OS configuration file +to use as fallback is none specific OS configuration is available using the +scheme _XX-default*.cmake_. Then is you need by example a module that isn't +named the same in one distro only, you only has to define a specific file to +handle that case then for all the other case put the configuration in the +default file. ## Include customs templated scripts -- cgit 1.2.3-korg