From: Andrey Ignatov <rdna@fb.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH bpf-next v4] tools/bpf: generate pkg-config file for libbpf
Date: Thu, 21 Mar 2019 16:00:46 +0000 [thread overview]
Message-ID: <20190321160042.GB13709@rdna-mbp> (raw)
In-Reply-To: <20190321102531.31810-1-luca.boccassi@gmail.com>
luca.boccassi@gmail.com <luca.boccassi@gmail.com> [Thu, 2019-03-21 03:26 -0700]:
> From: Luca Boccassi <bluca@debian.org>
>
> Generate a libbpf.pc file at build time so that users can rely
> on pkg-config to find the library, its CFLAGS and LDFLAGS.
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
> v2: use QUIET_GEN instead of QUIET_LINK to generate pc file,
> save kernel version in its own variable instead of calling
> make inline
> v3: use LIBBPF_VERSION instead of kernel_version
> v4: use -I${prefix}/include rather than -I${prefix}/include/bpf
> in the Cflags field as requested, to keep consistency with
> how the headers are used now and to avoid a dependency from
> the pc file to the headers installation
Thanks for the change Luca!
The other part about install target is nit, so no strong preference.
Acked-by: Andrey Ignatov <rdna@fb.com>
> tools/lib/bpf/.gitignore | 1 +
> tools/lib/bpf/Makefile | 18 +++++++++++++++---
> tools/lib/bpf/libbpf.pc.template | 11 +++++++++++
> 3 files changed, 27 insertions(+), 3 deletions(-)
> create mode 100644 tools/lib/bpf/libbpf.pc.template
>
> diff --git a/tools/lib/bpf/.gitignore b/tools/lib/bpf/.gitignore
> index 4db74758c674..7d9e182a1f51 100644
> --- a/tools/lib/bpf/.gitignore
> +++ b/tools/lib/bpf/.gitignore
> @@ -1,3 +1,4 @@
> libbpf_version.h
> +libbpf.pc
> FEATURE-DUMP.libbpf
> test_libbpf
> diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile
> index 61aaacf0cfa1..891fe3da1410 100644
> --- a/tools/lib/bpf/Makefile
> +++ b/tools/lib/bpf/Makefile
> @@ -80,6 +80,7 @@ libdir_SQ = $(subst ','\'',$(libdir))
> libdir_relative_SQ = $(subst ','\'',$(libdir_relative))
>
> LIB_FILE = libbpf.a libbpf.so
> +PC_FILE = libbpf.pc
>
> VERSION = $(BPF_VERSION)
> PATCHLEVEL = $(BPF_PATCHLEVEL)
> @@ -137,7 +138,7 @@ GLOBAL_SYM_COUNT = $(shell readelf -s --wide $(BPF_IN) | \
> VERSIONED_SYM_COUNT = $(shell readelf -s --wide $(OUTPUT)libbpf.so | \
> grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | sort -u | wc -l)
>
> -CMD_TARGETS = $(LIB_FILE)
> +CMD_TARGETS = $(LIB_FILE) $(PC_FILE)
>
> CXX_TEST_TARGET = $(OUTPUT)test_libbpf
>
> @@ -180,6 +181,12 @@ $(OUTPUT)libbpf.a: $(BPF_IN)
> $(OUTPUT)test_libbpf: test_libbpf.cpp $(OUTPUT)libbpf.a
> $(QUIET_LINK)$(CXX) $(INCLUDES) $^ -lelf -o $@
>
> +$(OUTPUT)libbpf.pc:
> + $(QUIET_GEN)sed -e "s|@PREFIX@|$(prefix)|" \
> + -e "s|@LIBDIR@|$(libdir_SQ)|" \
> + -e "s|@VERSION@|$(LIBBPF_VERSION)|" \
> + < $@.template > $@
> +
> check: check_abi
>
> check_abi: $(OUTPUT)libbpf.so
> @@ -209,7 +216,12 @@ install_headers:
> $(call do_install,libbpf.h,$(prefix)/include/bpf,644);
> $(call do_install,btf.h,$(prefix)/include/bpf,644);
>
> -install: install_lib
> +install_pkgconfig: $(PC_FILE)
> + $(call QUIET_INSTALL, $(PC_FILE)) \
> + $(call do_install,$(PC_FILE),$(libdir_SQ)/pkgconfig,644)
> +
> +
> +install: install_lib install_pkgconfig
>
> ### Cleaning rules
>
> @@ -219,7 +231,7 @@ config-clean:
>
> clean:
> $(call QUIET_CLEAN, libbpf) $(RM) $(TARGETS) $(CXX_TEST_TARGET) \
> - *.o *~ *.a *.so .*.d .*.cmd LIBBPF-CFLAGS
> + *.o *~ *.a *.so .*.d .*.cmd *.pc LIBBPF-CFLAGS
> $(call QUIET_CLEAN, core-gen) $(RM) $(OUTPUT)FEATURE-DUMP.libbpf
>
>
> diff --git a/tools/lib/bpf/libbpf.pc.template b/tools/lib/bpf/libbpf.pc.template
> new file mode 100644
> index 000000000000..0ecd334c109f
> --- /dev/null
> +++ b/tools/lib/bpf/libbpf.pc.template
> @@ -0,0 +1,11 @@
> +prefix=@PREFIX@
> +libdir=@LIBDIR@
> +includedir=${prefix}/include
> +
> +Name: libbpf
> +URL: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> +Description: Linux kernel BPF library
> +Version: @VERSION@
> +Libs: -L${libdir} -lbpf
> +Requires.private: libelf
> +Cflags: -I${includedir}
> --
> 2.20.1
>
--
Andrey Ignatov
next prev parent reply other threads:[~2019-03-21 16:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 21:06 [PATCH bpf-next] tools/bpf: generate pkg-config file for libbpf Luca Boccassi
2019-03-19 21:23 ` Stanislav Fomichev
2019-03-19 23:02 ` Luca Boccassi
2019-03-19 23:12 ` Stanislav Fomichev
2019-03-19 23:00 ` [PATCH bpf-next v2] " Luca Boccassi
2019-03-19 23:17 ` Stanislav Fomichev
2019-03-20 13:22 ` Luca Boccassi
2019-03-20 13:30 ` Luca Boccassi
2019-03-20 17:21 ` Stanislav Fomichev
2019-03-20 20:39 ` Luca Boccassi
2019-03-20 20:44 ` Stanislav Fomichev
2019-03-20 20:54 ` Daniel Borkmann
2019-03-20 21:13 ` Stanislav Fomichev
2019-03-20 13:28 ` [PATCH bpf-next v3] " luca.boccassi
2019-03-20 23:58 ` Andrey Ignatov
2019-03-21 10:29 ` Luca Boccassi
2019-03-21 10:25 ` [PATCH bpf-next v4] " luca.boccassi
2019-03-21 16:00 ` Andrey Ignatov [this message]
2019-03-21 22:01 ` Alexei Starovoitov
2019-03-21 22:19 ` Daniel Borkmann
2019-03-21 22:34 ` Luca Boccassi
2019-03-21 22:23 ` Luca Boccassi
2019-03-21 22:27 ` [PATCH bpf-next v5] " luca.boccassi
2019-03-21 22:33 ` [PATCH bpf-next v6] " luca.boccassi
2019-03-21 22:43 ` Alexei Starovoitov
2019-03-21 23:10 ` Luca Boccassi
2019-03-21 23:09 ` [PATCH bpf-next v7] " luca.boccassi
2019-03-26 20:12 ` Alexei Starovoitov
2019-03-26 20:17 ` Luca Boccassi
2019-03-28 11:33 ` [PATCH bpf-next v8] " luca.boccassi
2019-03-28 16:09 ` Daniel Borkmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190321160042.GB13709@rdna-mbp \
--to=rdna@fb.com \
--cc=luca.boccassi@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox