Tamir Duberstein fb41abe836 aya-build: infer BPF architecture from target ...

emit_bpf_target_arch_cfg defaults to HOST even when compiling for a
non-BPF target. On an AArch64 host, generating public API fixtures with
--target x86_64-unknown-linux-gnu therefore selects AArch64 bindings.

Use CARGO_CFG_TARGET_ARCH for non-BPF targets. Retain the HOST fallback
restored by 948b8553e for BPF, whose target triple identifies bytecode
endianness rather than the kernel's CPU. Explicit bpf_target_arch cfgs
and AYA_BPF_TARGET_ARCH continue to take precedence.

Only request environment-triggered reruns for AYA_BPF_TARGET_ARCH.
Cargo checks these directives against its own incoming environment, not
the values it supplies to build scripts [1].

[1]: https://doc.rust-lang.org/cargo/reference/build-scripts.html#rerun-if-env-changed

2026-08-27 05:05:32 -04:00

..

src

aya-build: infer BPF architecture from target

2026-08-27 05:05:32 -04:00

BUILD.bazel

build: add Bazel build and test graph

2026-06-25 12:36:47 -04:00

Cargo.toml

Release aya v0.14.0, aya-build v0.2.0, aya-ebpf-cty v0.3.0, aya-ebpf-bindings v0.2.0, aya-ebpf-macros v0.2.0, aya-ebpf v0.2.0, aya-log-common v0.2.0, aya-log v0.3.0, aya-log-parser v0.2.0, aya-log-ebpf-macros v0.2.0, aya-log-ebpf v0.2.0, safety bump 7 crates

2026-06-24 19:54:09 +02:00

CHANGELOG.md

chore: Fix typos

2026-06-24 21:01:25 +02:00