6 Commits (d31a1805daa1e44b9f91fcbf9230a56feadcf11b)

Author	SHA1	Message	Date
dependabot[bot]	4c78f7f1a0	build(deps): update object requirement from 0.30 to 0.31 ... Updates the requirements on [object](https://github.com/gimli-rs/object) to permit the latest version. - [Release notes](https://github.com/gimli-rs/object/releases) - [Changelog](https://github.com/gimli-rs/object/blob/master/CHANGELOG.md) - [Commits](https://github.com/gimli-rs/object/compare/0.30.0...0.31.0) --- updated-dependencies: - dependency-name: object dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>	1 year ago
Tamir Duberstein	33a0a2b604	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	1 year ago
Shenghui Ye	9c451a3357	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
Shenghui Ye	30f1fabc05	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
Shenghui Ye	ac49827e20	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
Shenghui Ye	81bc307dce	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