Lines Matching refs:generated_file
29 * [generated_file: Declare a generated_file target.](#func_generated_file)
135 * [output_conversion: Data format for generated_file targets.](#var_output_conversion)
1008 See `gn help generated_file` for more information on the walk.
1756 ### <a name="func_generated_file"></a>**generated_file**: Declare a generated_file target.
1821 If the following generated_file target is defined:
1823 generated_file("my_files_metadata") {
1840 generated_file target is defined:
1842 generated_file("my_files_metadata") {
1858 If `rebase` is used in the following generated_file target:
1860 generated_file("my_files_metadata") {
2702 Only copy, generated_file, and action targets are supported. The outputs from
2714 action, copy, and generated_file targets: this will just return the files
5254 The contents of the file for a generated_file target.
5255 See "gn help generated_file".
5360 See "gn help generated_file".
5903 ### <a name="var_output_conversion"></a>**output_conversion**: Data format for generated_file targe…
5906 Controls how the "contents" of a generated_file target is formatted.
6368 See also "gn help generated_file".
6568 If no walk_keys are specified for a generated_file target (i.e. "[""]"), the
6571 See "gn help generated_file".
7441 #### **generated_file targets**
7444 Similar to the write_file() function, the generated_file target type
7448 generated_file target type writes at target resolution time. See
7449 "gn help generated_file" for more detail.
7451 When written at target resolution time, generated_file enables GN to
7454 A generated_file target can declare either 'contents' to write statically
7465 generated_file aggregation targets. The 'metadata' scope must contain
7468 During the target resolution, generated_file targets will walk their
7473 The walk begins with the listed dependencies of the 'generated_file' target.
7475 of the 'generated_file' target's 'data_keys' list. If a match is found, the
7500 generated_file("metadata") {
7540 generated_file("metadata") {