aya/aya-obj/Cargo.toml

[package]
name = "aya-obj"
version = "0.1.0"
description = "An eBPF object file parsing library with BTF and relocation support."
keywords = ["bpf", "btf", "ebpf", "elf", "object"]
license = "MIT OR Apache-2.0"
authors = ["The Aya Contributors"]
repository = "https://github.com/aya-rs/aya"
readme = "README.md"
documentation = "https://docs.rs/aya-obj"
edition = "2021"

[dependencies]
bytes = { workspace = true }
core-error = { workspace = true, default-features = true }
hashbrown = { workspace = true, default-features = true }
log = { workspace = true }
object = { workspace = true, features = ["elf", "read_core"] }
thiserror = { workspace = true }

[dev-dependencies]
assert_matches = { workspace = true }
rbpf = { workspace = true }

[features]
std = []
aya-obj: migrate bindgen destination Aya::obj depends on bindgen generated files, and we start by migrating bindgen generated files. This commit adds the new aya-obj crate to the workplace and migrates generated files into the crate. We use core instead of std in an effort to make the final crate no_std. Bindgen was run against libbpf v1.0.1. Refs: #473 2 years ago			`[package]`
			`name = "aya-obj"`
aya-obj: update documentation and versioning info - Set the version number of `aya-obj` to `0.1.0`. - Update the description of the `aya-obj` crate. - Add a section in README and rustdoc warning about the unstable API. 2 years ago			`version = "0.1.0"`
			`description = "An eBPF object file parsing library with BTF and relocation support."`
Replace matches with assert_matches The matches crate has been archived now that `matches!` is in std. However `assert_matches!` is still unstable in std, and the assert_matches crate provides a more expressive form: ``` assert_matches!(foo, Ok(bar) => { assert_eq!(bar, baz); }); ``` 1 year ago			`keywords = ["bpf", "btf", "ebpf", "elf", "object"]`
aya-obj: migrate bindgen destination Aya::obj depends on bindgen generated files, and we start by migrating bindgen generated files. This commit adds the new aya-obj crate to the workplace and migrates generated files into the crate. We use core instead of std in an effort to make the final crate no_std. Bindgen was run against libbpf v1.0.1. Refs: #473 2 years ago			`license = "MIT OR Apache-2.0"`
			`authors = ["The Aya Contributors"]`
			`repository = "https://github.com/aya-rs/aya"`
			`readme = "README.md"`
			`documentation = "https://docs.rs/aya-obj"`
			`edition = "2021"`

			`[dependencies]`
cargo: Define dependencies on the workspace level This way we will avoid version mismatches and make differences in features across our crates clearer. 1 year ago			`bytes = { workspace = true }`
			`core-error = { workspace = true, default-features = true }`
			`hashbrown = { workspace = true, default-features = true }`
			`log = { workspace = true }`
Cargo.toml: remove redundant keys `default-features = false` is already in the root Cargo.toml. 1 year ago			`object = { workspace = true, features = ["elf", "read_core"] }`
			`thiserror = { workspace = true }`
aya-obj: migrate aya::obj into a separate crate To split the crate into two, several changes were made: 1. Most `pub(crate)` are now `pub` to allow access from Aya; 2. Parts of BpfError are merged into, for example, RelocationError; 3. BTF part of Features is moved into the new crate; 4. `#![deny(missing_docs)]` is removed temporarily; 5. Some other code gets moved into the new crate, mainly: - aya::{bpf_map_def, BtfMapDef, PinningType}, - aya::programs::{CgroupSock*AttachType}, The new crate is currenly allowing missing_docs. Member visibility will be adjusted later to minimize exposure of implementation details. Refs: #473 2 years ago
			`[dev-dependencies]`
cargo: Define dependencies on the workspace level This way we will avoid version mismatches and make differences in features across our crates clearer. 1 year ago			`assert_matches = { workspace = true }`
			`rbpf = { workspace = true }`
aya-obj: add no_std feature The crate has few libstd dependencies. Since it should be platform- independent in principle, making it no_std like the object crate would seem reasonable. However, the feature `error_in_core` is not yet stabilized, and the thiserror crate currently offers no no_std support. When the feature no_std is selected, we enable the `error_in_core` feature, switch to thiserror-core and replace the HashMap with the one in hashbrown. 2 years ago
			`[features]`
aya: flip feature "no_std" to feature "std" This fixes `cargo build --all-features` by sidestepping the feature unification problem described in The Cargo Book[0]. Add `cargo hack --feature-powerset` to CI to enforce that this doesn't regress (and that all combinations of features work). Since error_in_core is nightly-only, use core-error and a fake std module to allow aya-obj to build without std on stable. [0] https://doc.rust-lang.org/cargo/reference/features.html#feature-unification 2 years ago			`std = []`