You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
1 year ago | |
|---|---|---|
| .cargo | 1 year ago | |
| .github | 1 year ago | |
| xtask | 1 year ago | |
| {{project-name}} | 1 year ago | |
| {{project-name}}-common | 1 year ago | |
| {{project-name}}-ebpf | 1 year ago | |
| .gitignore | 1 year ago | |
| Cargo.toml | 1 year ago | |
| README.md | 1 year ago | |
| cargo-generate.toml | 2 years ago | |
| pre-script.rhai | 3 years ago | |
| rustfmt.toml | 1 year ago | |
| test.sh | 1 year ago | |
README.md
{{project-name}}
Prerequisites
- stable rust toolchains:
rustup toolchain install stable - nightly rust toolchains:
rustup toolchain install nightly --component rust-src - (if cross-compiling) rustup target:
rustup target add ${ARCH}-unknown-linux-musl - (if cross-compiling) LLVM: (e.g.)
brew install llvm(on macOS) - (if cross-compiling) C toolchain: (e.g.)
brew install filosottile/musl-cross/musl-cross(on macOS) - bpf-linker:
cargo install bpf-linker(--no-default-featureson macOS)
Build & Run
Use cargo build, cargo check, etc. as normal. Run your program with xtask run.
Cargo build scripts are used to automatically build the eBPF correctly and include it in the
program. When not using xtask run, eBPF code generation is skipped for a faster developer
experience; this compromise necessitates the use of xtask to actually build the eBPF.
Cross-compiling on macOS
Cross compilation should work on both Intel and Apple Silicon Macs.
AYA_BUILD_EBPF=true \
CC=${ARCH}-linux-musl-gcc \
RUSTFLAGS="-C linker=${ARCH}-linux-musl-gcc" \
cargo build --package {{project-name}} --release --target=${ARCH}-unknown-linux-musl
The cross-compiled program target/${ARCH}-unknown-linux-musl/release/{{project-name}} can be
copied to a Linux server or VM and run there.