package cc_analyzer

Get desktop application:
View/edit binary Protocol Buffers messages

Provides all the targets that are pre-requisities for running language services on active_file_paths.

• repeated DepsResponse.Deps deps = 1

• optional Status status = 2

Build dependencies of a source file for providing language services.

Used in: DepsResponse

• string source_file = 1

  Relative to repo_dir.

• repeated string build_target = 2

  Build target to execute for generating dep.

• optional Status status = 3

Returns all the information necessary for providing language services for the active files.

Used in: SourceFile

• string path = 1

  Path to the file relative to repository root.

• optional bytes contents = 2

  The text of the generated file, if not provided contents will be read from the path above in user's workstation.

• repeated SourceFile sources = 2

• optional Status status = 3

  Status representing overall analysis. Should fail only when no analysis can be performed.

Represents an Android checkout on user's workstation.

• string repo_dir = 1

  Absolute path for the checkout in the workstation. e.g. /home/user/work/android/

• repeated string active_file_path = 2

  Relative to repo_dir.

• string out_dir = 3

  Repository relative path to output directory in workstation.

• string comp_db_path = 4

  Repository relative path to compile_commands.json in workstation.

Used in: IdeAnalysis

• string path = 1

  Path to the source file relative to repository root.

• string working_dir = 2

  Working directory used by the build system. All the relative paths in compiler_arguments should be relative to this path. Relative to repository root.

• repeated string compiler_arguments = 3

  Compiler arguments to compile the source file. If multiple variants of the module being compiled are possible, the query script will choose one.

• repeated GeneratedFile generated = 4

  Any generated files that are used in compiling the file.

• repeated string deps = 5

  Paths to all of the sources, like build files, code generators, proto files etc. that were used during analysis. Used to figure out when a set of build artifacts are stale and the query tool must be re-run. Relative to repository root.

• optional Status status = 6

  Represents analysis status for this particular file. e.g. not part of the build graph.

Indicates the success/failure for analysis.

Used in: DepsResponse, DepsResponse.Deps, IdeAnalysis, SourceFile

• Status.Code code = 1

• optional string message = 2

  Details about the status, might be displayed to user.

Used in: Status

• OK = 0

• FAILURE = 1