cloud-hypervisor/vendor/registry-40351f815f426200/bitflags
Samuel Ortiz d5f5648b37 vendor: Add vendored dependencies
We use cargo vendor to generate a .cargo/config file and the vendor
directory. Vendoring allows us to lock our dependencies and to modify
them easily from the top level Cargo.toml.

We vendor all dependencies, including the crates.io ones, which allows
for network isolated builds.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-04 17:51:52 +02:00
..
src vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
.cargo-checksum.json vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
Cargo.toml vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
CHANGELOG.md vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
CODE_OF_CONDUCT.md vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
LICENSE-APACHE vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
LICENSE-MIT vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
README.md vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00

bitflags

Build Status Join the chat at https://gitter.im/bitflags/Lobby Latest version Documentation Minimum rustc version License

A Rust macro to generate structures which behave like a set of bitflags

Usage

Add this to your Cargo.toml:

[dependencies]
bitflags = "1.0"

and this to your crate root:

#[macro_use]
extern crate bitflags;

Rust Version Support

The minimum supported Rust version is 1.20 due to use of associated constants.