On 9/2/22 12:22 AM, Daniel Müller wrote:
BPF object files are, in a way, the final artifact produced as part of the ahead-of-time compilation process. That makes them somewhat special compared to "regular" object files, which are a intermediate build artifacts that can typically be removed safely. As such, it can make sense to name them differently to make it easier to spot this difference at a glance. Among others, libbpf-bootstrap [0] has established the extension .bpf.o for BPF object files. It seems reasonable to follow this example and establish the same denomination for selftest build artifacts. To that end, this change adjusts the corresponding part of the build system and the test programs loading BPF object files to work with .bpf.o files. [0] https://github.com/libbpf/libbpf-bootstrap Changelog: v2 -> v3: - adjusted msg call to use proper extension substitution - adjusted examples in README.rst to use new extension v1 -> v2: - fixed up subject; it's only a single patch Signed-off-by: Daniel Müller <deso@xxxxxxxxxx> Suggested-by: Andrii Nakryiko <andrii@xxxxxxxxxx>
Applied and fixed up the checkpatch warnings along the way (modulo exceeds 80 columns and %s... ones): https://patchwork.hopto.org/static/nipa/673411/12963406/checkpatch/summary Thanks, Daniel
