Get desktop application:
View/edit binary Protocol Buffers messages
Represents a single action, which is a function from Artifact(s) to Artifact(s).
Used in:
The target that was responsible for the creation of the action.
The aspects that were responsible for the creation of the action (if any). In the case of aspect-on-aspect, AspectDescriptors are listed in topological order of the dependency graph. e.g. [A, B] would imply that aspect A is applied on top of aspect B.
Encodes all significant behavior that might affect the output. The key must change if the work performed by the execution of this action changes. Note that the key doesn't include checksums of the input files.
The mnemonic for this kind of action.
The configuration under which this action is executed.
The command line arguments of the action. This will be only set if explicitly requested.
The list of environment variables to be set before executing the command.
The set of input dep sets that the action depends upon. If the action does input discovery and `--include_pruned_outputs` is disabled, the contents of this set might differ before and after execution.
The list of Artifact IDs that represent the output files that this action will generate.
True iff the action does input discovery during execution.
Execution info for the action. Remote execution services may use this information to modify the execution environment, but actions will generally not be aware of it.
The list of param files. This will be only set if explicitly requested.
The id to an Artifact that is the primary output of this action.
The execution platform for this action. Empty if the action has no execution platform.
The template content of the action, if it is TemplateExpand action.
The list of substitution should be performed on the template. The key is the string to be substituted and the value is the string to be substituted to.
The contents of the file for the ctx.actions.write() action (guarded by the --include_file_write_contents flag).
The target of the symlink created by UnresolvedSymlink actions. For regular Symlink actions, the target is represented as an input.
If FileWrite actions should make their output executable. (ctx.actions.write(is_executable=True))
Container for the action graph properties.
Represents a single artifact, whether it's a source file or a derived output file.
Used in:
Identifier for this artifact; this is a uint32, only valid for this particular dump of the analysis.
The id of the PathFragment that represents the relative path of the file within the execution root.
True iff the artifact is a tree artifact, i.e. the above exec_path refers a directory.
Represents an invocation specific descriptor of an aspect.
Used in:
Identifier for this aspect descriptor; this is a uint32, only valid for the particular dump of the analysis.
The name of the corresponding aspect. For native aspects, it's the Java class name, for Starlark aspects it's the bzl file followed by a % sign followed by the name of the aspect.
The list of parameters bound to a particular invocation of that aspect on a target. Note that aspects can be executed multiple times on the same target in different order.
Used in: , ,
Identifier for this configuration; this is a uint32, only valid for the particular dump of the analysis.
The mnemonic representing the build configuration.
The platform string.
The checksum representation of the configuration options;
Whether this configuration is used for building tools.
The configuration fragments that are a part of this configuration.
The union of all the FragmentOptions associated with the Fragments that are a part of this configuration. These are returned separately from the fragments field because a set of FragmentOptions can be referenced by more than one Fragment, and we wish to avoid returning the same FragmentOptions repeatedly. These are sorted by the FragmentOptions name field.
Used in:
The target. We use blaze_query.Target defined in build.proto instead of the Target defined in this file because blaze_query.Target is much heavier and will output proto results similar to what users are familiar with from regular blaze query.
DEPRECATED. Use configuration_id instead.
The id of the configuration this target is configured for. The actual Configuration message can be found in CqueryResults. If the target doesn't have a configuration, the value will be 0.
Container for cquery results
All the configuredtargets returns by cquery
All the Configurations referenced by results.
Used in:
Identifier for this named set of files; this is a uint32, only valid for the particular dump of the analysis.
Other transitively included named set of files.
The list of input artifact IDs that are immediately contained in this set.
A configuration fragment (http://bazel.build/rules/lib/fragments).
Used in:
The name of the Fragment.
The names of the FragmentOptions associated with this fragment in sorted order.
A set of fragment options.
Used in:
The name of this set of fragment options.
The options themselves, in sorted order by name.
Used in: ,
The variable name.
The variable value.
A fragment option.
Used in:
The name of the option.
The value of the option.
Content of a param file.
Used in:
The exec path of the param file artifact.
The arguments in the param file. Each argument corresponds to a line in the param file.
The path fragment that makes up a full path.
Used in:
Identifier for this path fragment.
The label of the section in the path.
The id of the parent path fragment.
Used in:
Identifier for this rule class; this is a uint32, only valid for this particular dump of the analysis.
Name of the rule class, e.g. cc_library.
Represents a single target (without configuration information) that is associated with an action.
Used in:
Identifier for this target; this is a uint32, only valid for this particular dump of the analysis.
Label of the target, e.g. //foo:bar.
Class of the rule.