Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(515)

Unified Diff: tools/gn/docs/reference.md

Issue 1346653004: Fix some typos in gn's documentation for "copy". (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Rerun "gn help --markdown all > tools/gn/docs/reference.md" Created 5 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | tools/gn/functions_target.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: tools/gn/docs/reference.md
diff --git a/tools/gn/docs/reference.md b/tools/gn/docs/reference.md
index 8cd25ab5ba9cf74210ba31d06bd60e6a9f4437a1..0eea4d56c1aa90a1069343fa8d4c552a460625fb 100644
--- a/tools/gn/docs/reference.md
+++ b/tools/gn/docs/reference.md
@@ -1045,15 +1045,15 @@
reference the output or generated intermediate file directories,
respectively.
- Both "sources" and "outputs" must be specified. Sources can
+ Both "sources" and "outputs" must be specified. Sources can include
as many files as you want, but there can only be one item in the
outputs list (plural is used for the name for consistency with
other target types).
If there is more than one source file, your output name should specify
- a mapping from each source files to output file names using source
+ a mapping from each source file to an output file name using source
expansion (see "gn help source_expansion"). The placeholders will
- will look like "{{source_name_part}}", for example.
+ look like "{{source_name_part}}", for example.
```
@@ -3518,8 +3518,8 @@
A list of target labels.
Specifies dependencies of a target that are not actually linked into
- the current target. Such dependencies will be built and will be available
- at runtime.
+ the current target. Such dependencies will be built and will be
+ available at runtime.
This is normally used for things like plugins or helper programs that
a target needs at runtime.
@@ -3778,6 +3778,25 @@
to dependent targets, put them in a config and set it in the
all_dependent_configs or public_configs.
+```
+
+### **Ordering of flags and values**:
eroman 2015/09/15 17:57:26 Not sure why this change was added. I generated t
+
+```
+ 1. Those set on the current target (not in a config).
+ 2. Those set on the "configs" on the target in order that the
+ configs appear in the list.
+ 3. Those set on the "all_dependent_configs" on the target in order
+ that the configs appear in the list.
+ 4. Those set on the "public_configs" on the target in order that
+ those configs appear in the list.
+ 5. all_dependent_configs pulled from dependencies, in the order of
+ the "deps" list. This is done recursively. If a config appears
+ more than once, only the first occurance will be used.
+ 6. public_configs pulled from dependencies, in the order of the
+ "deps" list. If a dependency is public, they will be applied
+ recursively.
+
```
## **lib_dirs**: Additional library directories.
« no previous file with comments | « no previous file | tools/gn/functions_target.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698