Searched refs:expansion (Results 1 – 4 of 4) sorted by relevance
/tools/tradefederation/core/src/com/android/tradefed/command/ |
D | CommandFileParser.java | 283 CommandLine expansion = new CommandLine(lArgs.subList(3, lArgs.size()), in scanFile() local 285 CommandLine prev = mMacros.put(name, expansion); in scanFile() 288 CLog.w("value '%s' replaced previous value '%s'", expansion, prev); in scanFile() 293 List<CommandLine> expansion = new LinkedList<CommandLine>(); in scanFile() local 309 expansion.add(line); in scanFile() 316 CLog.d("Parsed %d-line definition for long macro %s", expansion.size(), in scanFile() 319 List<CommandLine> prev = mLongMacros.put(name, expansion); in scanFile() 323 expansion.size(), prev.size()); in scanFile() 442 List<CommandLine> expansion = new LinkedList<CommandLine>(); in expandLongMacro() local 468 expansion.add(expanded); in expandLongMacro() [all …]
|
/tools/asuite/atest/bazel/runner/src/main/protobuf/ |
D | invocation_policy.proto | 25 // After expanding policies on expansion flags or flags with implicit 75 // flags, but are actually Void expansion flags that expand into other flags. 78 // "--novoid_flag" which is also an expansion flag with the type Void whose 80 // are the opposite of "--void_flag". For expansion flags, it's best to 109 // from command line/config expansion/rc files. 133 // returns the default. This is mostly relevant for expansion flags: it will 134 // erase user values in *all* flags that the expansion flag expands to. Only 135 // use this on expansion flags if this is acceptable behavior. Since the last 138 // use this on expansion flags at all.
|
D | command_line.proto | 70 // example, include expansion flags as they are. However, if this option 72 // understands them, then the expansion flag, which has no value, would not
|
D | build_event_stream.proto | 87 // have been skipped for some reason, if the actual expansion was still 103 // If empty, the id refers to the expansion of the target. If not-empty, 104 // the id refers to the expansion of an aspect applied to the (already 417 // Payload of the event indicating the expansion of a target pattern. 450 // been identified. As with pattern expansion the main information is in the
|