qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [RISU PATCH 06/10] configure: support CPPFLAGS


From: Alex Bennée
Subject: [Qemu-devel] [RISU PATCH 06/10] configure: support CPPFLAGS
Date: Tue, 7 Nov 2017 15:05:54 +0000

Useful for accessing API's that are still brewing, e.g:

  CROSS_PREFIX=aarch64-linux-gnu- \
    CPPFLAGS=-I/home/alex/lsrc/qemu/risu.git/sve-headers/include \
    ../configure

Signed-off-by: Alex Bennée <address@hidden>
---
 README    | 6 ++++++
 configure | 1 +
 2 files changed, 7 insertions(+)

diff --git a/README b/README
index 9946e6e..fbe408d 100644
--- a/README
+++ b/README
@@ -26,6 +26,12 @@ Most useful is
    need this if you're not building on the target system
    (Example: CROSS_PREFIX=arm-linux-gnueabihf- )
 
+Another useful flag is
+ CPPFLAGS= which specified pre-processor flags, usually -I statements
+   for specifying extra include paths. Use this is you need something
+   from new kernel headers not installed on your system.
+   (Example: CPPFLAGS=-I/path/to/sve-kernel-headers/include)
+
 Passing --static will build a statically linked binary which is useful
 if you don't want to mess around with a chroot to run the binary.
 
diff --git a/configure b/configure
index c622a5e..65e1819 100755
--- a/configure
+++ b/configure
@@ -111,6 +111,7 @@ generate_makefilein() {
     echo "# Makefile.in - generated by the 'configure' script" > $m
     echo "ARCH:=${ARCH}" >> $m
     echo "CC:=${CC}" >> $m
+    echo "CPPFLAGS:=${CPPFLAGS}" >> $m
     echo "LDFLAGS:=${LDFLAGS}" >> $m
     echo "AS:=${AS}" >> $m
     echo "OBJCOPY:=${OBJCOPY}" >> $m
-- 
2.14.2




reply via email to

[Prev in Thread] Current Thread [Next in Thread]