|
|
@ -2019,11 +2019,13 @@ A build target is either an [executable](#executable), |
|
|
|
previous versions. The default will eventually be changed to `true` |
|
|
|
previous versions. The default will eventually be changed to `true` |
|
|
|
in a future version. |
|
|
|
in a future version. |
|
|
|
|
|
|
|
|
|
|
|
- `extract_objects()` returns an opaque value representing the |
|
|
|
- `extract_objects(source1, source2, ...)` takes as its arguments |
|
|
|
generated object files of arguments, usually used to take single |
|
|
|
a number of source files as [`string`](#string-object) or |
|
|
|
object files and link them to unit tests or to compile some source |
|
|
|
[`files()`](#files) and returns an opaque value representing the |
|
|
|
files with custom flags. To use the object file(s) in another build |
|
|
|
object files generated for those source files. This is typically used |
|
|
|
target, use the `objects:` keyword argument. |
|
|
|
to take single object files and link them to unit tests or to compile |
|
|
|
|
|
|
|
some source files with custom flags. To use the object file(s) |
|
|
|
|
|
|
|
in another build target, use the `objects:` keyword argument. |
|
|
|
|
|
|
|
|
|
|
|
- `full_path()` returns a full path pointing to the result target file. |
|
|
|
- `full_path()` returns a full path pointing to the result target file. |
|
|
|
NOTE: In most cases using the object itself will do the same job as |
|
|
|
NOTE: In most cases using the object itself will do the same job as |
|
|
|