5 Commits (09fa11fa3038847a290e28853cff9ed04b47bd37)

Author	SHA1	Message	Date
Tamir Duberstein	0168396604	integration-ebpf: add cargo config ... Same reasoning as the one in bpf.	2 years ago
Tamir Duberstein	b86d42d1b0	xtask: remove assumptions from docs command ... This slightly changes the site layout: crate documentation is now flat rather than being nested under "user" and "bpf". - Run `cargo clean --doc` before generating docs to ensure hermiticity. - Generate header.html into a temporary directory. - Remove "site" on each run to ensure hermiticity. - Invoke cargo only once. - Avoid editing sources.	2 years ago
Alessandro Decina	c64d8e2bb7	Add back bpf/.cargo/config.toml ... So to build/check things using the bpf target one can: cd bpf && cargo check && cargo build without having to manually pass --target=bpfel-unknown-none -Z build-std=core. It also fixes cargo xtask docs, since the command relies on bpf docs being built with the bpfel-unknown-none target.	2 years ago
Tamir Duberstein	6ca7d53733	Remove detritus ... - rustfmt settings are hierarchical. - integration-ebpf is always compiled at a distance with flags provided. - .cargo/config.toml is not respected except at the root of the workspace[0]. [0] https://doc.rust-lang.org/cargo/reference/config.html#hierarchical-structure	2 years ago
Dave Tucker	dc31e11691	Re-organize into a single workspace ... This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>	3 years ago