blob: 0d8957e35a391d64e64c6119d005671a27542bcb (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
# Advanced customization
## Including additionnals cmake files
Advanced tuning is possible using addionnals cmake files that are included
automatically from some specifics locations. They are included in that order:
- Project CMake files normaly located in _<project-root-path>/conf.d/app-templates/cmake/cmake.d_
- Home CMake files located in _$HOME/.config/app-templates/cmake.d_
- System CMake files located in _/etc/app-templates/cmake.d_
CMake files has to be named using the following convention: `XX-common-*.cmake`
or `XX-${PROJECT_NAME}-*.cmake`, where `XX` are numbers, `*` file name
(ie. `99-common-my_customs.cmake`).
> **NOTE** You need to specify after numbers that indicate include order, to
which project that file applies, if it applies to all project then use keyword
`common`.
So, saying that you should be aware that every normal cmake variables used at
project level could be overwrited by home or system located cmake files if
variables got the same name. Exceptions are cached variables set using
**CACHE** keyword:
Example:
```cmake
set(VARIABLE_NAME 'value string random' CACHE STRING 'docstring')
```
## Include customs templated scripts
As well as for additionnals cmake files you can include your own templated
scripts that will be passed to cmake command `configure_file`.
Just create your own script to the following directories:
- Home location in _$HOME/.config/app-templates/scripts_
- System location in _/etc/app-templates/scripts_
Scripts only needs to use the extension `.in` to be parsed and configured by
CMake command.
|
