Lines Matching refs:a
3 `cargo_embargo` is a tool to generate `Android.bp` files automatically for external Rust crates
5 `cargo_embargo generate cargo_embargo.json` in a directory containing one or more Rust packages. If
10 `cargo_embargo` is configured with a JSON configuration file usually called `cargo_embargo.json`.
11 This can contain a number of options, specified at several levels. A config may cover one or more
12 packages, and have one or more variants. All packages under `external/rust/crates` use a separate
13 `cargo_embargo.json` file per package, but other users (such as crosvm) may use a single
14 `cargo_embargo.json` for a tree of many packages. Most configurations have a single variant, but
15 multiple variants are used in some cases to provide both `std` and `no_std` variants of a package.
17 The overall structure of a config file looks like this:
24 // Options for all variants of a package.
32 // Options for a specific variant of all packages.
35 // Options for a specific variant of a specific package.
46 If a package is not included in the `package` map then it is assumed to use default options. If the
48 there is assumed to be a single variant. Thus `{}` is a valid config file for a single variant with
51 A typical config file for a simple package may look like:
60 This expands to a single variant with the given options, and all packages (i.e. the only one) using
82 … | Map of renames for modules. For example, if a "libfoo" would be ge…
91 packages with a `build.rs`, so it is recommended to run with `run_cargo` set to `true` initially,
97 specified outside of a package.
106 | `host_first_multilib` | boolean | `false` | yes | Add a `compile_mult…
112 … | `false` | yes | Copy `build.rs` output to `./out/*` and add a genrule to copy `./o…
119 For importing a new package, you may start by running cargo_embargo's autoconfig mode:
125 This will attempt to generate a suitable `cargo_embargo.json` for the package in the current