Since `build_always` also adds a target to the set of default targets, this option is marked deprecated in favour of the new option `build_always_stale`. `build_always_stale` *only* marks the target to be always considered out of date, but does *not* add it to the set of default targets. The old behaviour can still be achieved by combining `build_always_stale` with `build_by_default`. fixes #1942pull/3752/head
parent
d7466066e4
commit
cbe18e01e4
6 changed files with 34 additions and 11 deletions
@ -0,0 +1,12 @@ |
||||
## Deprecate `build_always` |
||||
|
||||
Setting `build_always` to `true` for a custom target not only marks the target |
||||
to be always considered out of date, but also adds it to the set of default |
||||
targets. This option is therefore deprecated and the new option |
||||
`build_always_stale` is introduced. |
||||
|
||||
`build_always_stale` *only* marks the target to be always considered out of |
||||
date, but does not add it to the set of default targets. The old behaviour can |
||||
be achieved by combining `build_always_stale` with `build_by_default`. |
||||
|
||||
The documentation has been updated accordingly. |
Loading…
Reference in new issue