Lines Matching refs:package

13 `cargo_embargo.json` file per package, but other users (such as crosvm) may use a single
15 multiple variants are used in some cases to provide both `std` and `no_std` variants of a package.
22   "package": {
24       // Options for all variants of a package.
33       "package": {
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
47 `package` map is omitted then all packages will use default options. If `variants` is omitted then
51 A typical config file for a simple package may look like:
94 ### Per-package configuration options
96 These options may be specified per package. Most may also be overridden per variant. They may not be
97 specified outside of a package.
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