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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
# Configuration
If there are multiple configuration options, passing them through compiler flags becomes very burdensome. It also makes the configuration settings hard to inspect. To make things easier, Meson supports the generation of configure files. This feature is similar to one found in other build systems such as CMake.
Suppose we have the following Meson snippet:
```meson
conf_data = configuration_data()
conf_data.set('version', '1.2.3')
configure_file(input : 'config.h.in',
output : 'config.h',
configuration : conf_data)
```
and that the contents of `config.h.in` are
```c
#define VERSION_STR "@version@"
```
Meson will then create a file called `config.h` in the corresponding build directory whose contents are the following.
```c
#define VERSION_STR "1.2.3"
```
More specifically, Meson will find all strings of the type `@varname@` and replace them with respective values set in `conf_data`. You can use a single `configuration_data` object as many times as you like, but it becomes immutable after the first use. That is, after it has been used once the `set` function becomes unusable and trying to call it causes an error.
For more complex configuration file generation Meson provides a second form. To use it, put a line like this in your configuration file.
#mesondefine TOKEN
The replacement that happens depends on what the value and type of TOKEN is:
```c
#define TOKEN // If TOKEN is set to boolean true.
#undef TOKEN // If TOKEN is set to boolean false.
#define TOKEN 4 // If TOKEN is set to an integer or string value.
/* undef TOKEN */ // If TOKEN has not been set to any value.
```
Note that if you want to define a C string, you need to do the quoting yourself like this:
```meson
conf.set('TOKEN', '"value"')
```
Since this is such a common operation, Meson provides a convenience method:
```meson
plain_var = 'value'
conf.set_quoted('TOKEN', plain_var) # becomes #define TOKEN "value"
```
Often you have a boolean value in Meson but need to define the C/C++ token as 0 or 1. Meson provides a convenience function for this use case.
```meson
conf.set10(token, boolean_value)
# The line above is equivalent to this:
if boolean_value
conf.set(token, 1)
else
conf.set(token, 0)
endif
```
## Configuring without an input file
If the input file is not defined then Meson will generate a header file all the entries in the configuration data object. The replacements are the same as when generating `#mesondefine` entries:
```meson
cdata.set('FOO', '"string"') => #define FOO "string"
cdata.set('FOO', 'a_token') => #define FOO a_token
cdata.set('FOO', true) => #define FOO
cdata.set('FOO', false) => #undef FOO
cdata.set('FOO', 1) => #define FOO 1
cdata.set('FOO', 0) => #define FOO 0
```
In this mode, you can also specify a comment which will be placed before the value so that your generated files are self-documenting.
```meson
cdata.set('BAR', true, description : 'Set BAR if it is available')
```
Will produce:
```c
/* Set BAR if it is available */
#define BAR
```
|
