libbpf

6 Commits

Author	SHA1	Message	Date
hex	6a7b28b6a1	libbpf: fix extraversion in Makefile The current LIBBPF_VERSION (0.0.3) doesn't match with ABI version LIBBPF_0.0.4. Fix the EXTRAVERSION portion.	2019-07-31 21:56:11 -07:00
hex	816253000e	Travis CI: add gcc-8, gcc-8 ASan+UBSan tests	2019-04-30 11:39:37 -07:00
hex	7ed7e4f0ad	Embed Travis CI status image into libbpf README Show the build status in a convenient way. Follow the instructions: https://docs.travis-ci.com/user/status-images/	2019-04-30 11:39:37 -07:00
hex	4de9ffcffe	Travis CI folow up Fix ENV_VARS passing to `docker` so `CC` is set to `clang`. Fix asan compiler option. Specify all compiler options in `CFLAGS`. Related discussion https://github.com/libbpf/libbpf/pull/36#discussion_r276522335	2019-04-30 11:39:37 -07:00
hex	2d1959ff60	Introduce Travis CI tests In order to libbpf to be used in systemd some testing is required, see related discussions in https://github.com/systemd/systemd/pull/12151 and https://github.com/libbpf/libbpf/pull/29 The tests introduced here mirrors the tests of systemd: For Debian: build with gcc, gcc + asan, clang, clang + asan Debian tests use `docker` virtualization Fror Ubuntu Xenial: build with gcc The differences: Install only libelf and it's dependencies. Instead of Meson build system `make` is used, so `make` remains the preferred method of building and `meson.build` doesn't get rooted in `libbpf`. `travis_wait.bash` is kept as a workaround for https://github.com/travis-ci/travis-ci/issues/9979 An example of testing UI: https://travis-ci.org/wat-ze-hex/libbpf	2019-04-17 14:19:40 -07:00
hex	65b4e9359a	add meson.build for meson build system Make it possible to include libbpf into projects built by Meson build system as a subproject. This is the case e.g. for systemd. meson.build declares dependencies which may be used in parent projects: `libbpf_static_dep` for static library `libbpf_shared_dep` for shared library `bpf_includes` provides the location of bpf.h, btf.h and libbpf.h Parent projects need to introduce git wrap to build libbpf: https://github.com/mesonbuild/meson/blob/master/docs/markdown/Wrap-dependency-system-manual.md#wrap-git An alternative approach is applying a patch with meson.build for libbpf while building a parent project: https://github.com/mesonbuild/meson/blob/master/docs/markdown/Wrap-dependency-system-manual.md#wrap-file Imo it's less transparent and would add more headache. meson.build is placed in the source root because that's how Meson expects it to be placed. The related discussion is in https://github.com/systemd/systemd/pull/12151	2019-04-15 21:39:11 -07:00