From: Andrii Nakryiko <andrii@kernel.org>
To: <dwarves@vger.kernel.org>, <acme@kernel.org>
Cc: <andrii@kernel.org>
Subject: [PATCH dwarves] cmake: make libbpf's Linux UAPI headers available to all binaries
Date: Sat, 24 Oct 2020 11:36:53 -0700 [thread overview]
Message-ID: <20201024183653.891042-1-andrii@kernel.org> (raw)
Now that libbpf is used to implement deduplicated strings container, all of
the binaries will need linux/btf.h header to compile properly. libbpf is
distributed with its own copies of Linux UAPI headers, so use them during
compilation.
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
---
CMakeLists.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 8e9fe4710a0c..84693514e0c8 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -2,7 +2,9 @@ project(pahole C)
cmake_minimum_required(VERSION 2.8.8)
cmake_policy(SET CMP0005 NEW)
-INCLUDE_DIRECTORIES( ${CMAKE_CURRENT_BINARY_DIR} ${CMAKE_CURRENT_SOURCE_DIR} )
+INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR}
+ ${CMAKE_CURRENT_SOURCE_DIR}
+ ${CMAKE_CURRENT_SOURCE_DIR}/lib/bpf/include/uapi)
# Try to parse this later, Helio just showed me a KDE4 example to support
# x86-64 builds.
--
2.24.1
next reply other threads:[~2020-10-24 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 18:36 Andrii Nakryiko [this message]
2020-10-26 19:49 ` [PATCH dwarves] cmake: make libbpf's Linux UAPI headers available to all binaries Arnaldo Carvalho de Melo
2020-10-26 23:26 ` Andrii Nakryiko
2020-10-27 11:20 ` Arnaldo Carvalho de Melo
2020-10-27 12:22 ` Arnaldo Carvalho de Melo
2020-10-27 18:02 ` Andrii Nakryiko
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=20201024183653.891042-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=acme@kernel.org \
--cc=dwarves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).