platform_build/tools/aconfig/Cargo.toml

[package]
name = "aconfig"
version = "0.1.0"
edition = "2021"
build = "build.rs"

[features]
default = ["cargo"]
cargo = []

[dependencies]
anyhow = "1.0.69"
protobuf = "3.2.0"

[build-dependencies]
protobuf-codegen = "3.2.0"
aconfig: add support for cargo Officially, aconfig is build using the Android tool-chain. However, to speed up the local development cycle, add support for building with cargo. While it is possible to tell cargo to place the build artifacts outside the source tree, there is no way to tell it to not generate the cargo lock file in the same directory as Cargo.toml. Add a .gitignore to ignore Cargo.lock and the target directory. The way the Android build system and cargo generates code from the protobuf files is slightly different. Tell cargo to enable the "cargo" feature and introduce src/protos.rs to hide this difference from the rest of the aconfig source. Bug: 279485059 Test: m aconfig && aconfig Test: atest aconfig.test Test: cargo build Test: cargo test Change-Id: I85741f58cadae353ed95c124f566e4f4a7484186 2023-04-26 09:13:03 +02:00			`[package]`
			`name = "aconfig"`
			`version = "0.1.0"`
			`edition = "2021"`
			`build = "build.rs"`

			`[features]`
			`default = ["cargo"]`
			`cargo = []`

			`[dependencies]`
aconfig: define Aconfig proto Fill in aconfig.proto. Define Aconfig definitions (for introducing flags and setting their values) and Overrides (for overriding flags regardless of what their definitions say). More changes to the proto schema are expected when more of the aconfig project is outlined. Use proto2 instead of proto3: this will cause the protobuf text parser to error on missing fields instead of returning a default value which is ambiguous, especially for booleans. (Also, the text protobuf parser doesn't provide good error messages: if the input is missing a field, the error is always "1:1: Message not initialized"). Unfortunately the generated Rust wrappers around the proto structs land in an external crate, which prevents aconfig from adding new impl blocks. Circumvent this by converting the data read from proto into structs defined in the aconfig crate. Change main.rs to parse (static) text proto. Also add dependency on anyhow. Bug: 279485059 Test: atest aconfig.test Change-Id: I512e3b61ef20e2f55b7699a178d466d2a9a89eac 2023-04-26 13:16:41 +02:00			`anyhow = "1.0.69"`
aconfig: add support for cargo Officially, aconfig is build using the Android tool-chain. However, to speed up the local development cycle, add support for building with cargo. While it is possible to tell cargo to place the build artifacts outside the source tree, there is no way to tell it to not generate the cargo lock file in the same directory as Cargo.toml. Add a .gitignore to ignore Cargo.lock and the target directory. The way the Android build system and cargo generates code from the protobuf files is slightly different. Tell cargo to enable the "cargo" feature and introduce src/protos.rs to hide this difference from the rest of the aconfig source. Bug: 279485059 Test: m aconfig && aconfig Test: atest aconfig.test Test: cargo build Test: cargo test Change-Id: I85741f58cadae353ed95c124f566e4f4a7484186 2023-04-26 09:13:03 +02:00			`protobuf = "3.2.0"`

			`[build-dependencies]`
			`protobuf-codegen = "3.2.0"`