]>
Commit | Line | Data |
---|---|---|
b32b8144 FG |
1 | # Copyright 2017 Rene Rivera |
2 | # Distributed under the Boost Software License, Version 1.0. | |
3 | # (See accompanying file LICENSE_1_0.txt or copy at | |
4 | # http://www.boost.org/LICENSE_1_0.txt) | |
5 | ||
b32b8144 FG |
6 | import feature ; |
7 | ||
f67539c2 TL |
8 | #| tag::doc[] |
9 | ||
10 | [[bbv2.builtin.features.tag]]`tag`:: | |
11 | Used to customize the name of the generated files. The value should have the | |
12 | form: | |
13 | + | |
14 | ---- | |
15 | @rulename | |
16 | ---- | |
17 | + | |
18 | where _rulename_ should be a name of a rule with the following signature: | |
19 | + | |
20 | ---- | |
21 | rule tag ( name : type ? : property-set ) | |
22 | ---- | |
23 | + | |
24 | The rule will be called for each target with the default name computed by | |
25 | B2, the type of the target, and property set. The rule can either | |
26 | return a string that must be used as the name of the target, or an empty | |
27 | string, in which case the default name will be used. | |
28 | + | |
29 | Most typical use of the `tag` feature is to encode build properties, or library | |
30 | version in library target names. You should take care to return non-empty | |
31 | string from the tag rule only for types you care about -- otherwise, you might | |
32 | end up modifying names of object files, generated header file and other targets | |
33 | for which changing names does not make sense. | |
34 | ||
35 | |# # end::doc[] | |
36 | ||
b32b8144 FG |
37 | feature.feature tag |
38 | : | |
39 | : free ; |