From: robert.foss@collabora.com
To: daniel.vetter@ffwll.ch, daniel.stone@collabora.com,
marius.c.vlad@intel.com, tomeu.vizoso@collabora.com,
emil.l.velikov@gmail.com, chris@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org
Subject: [RFC i-g-t 2/2] overlay/Makefile: Don't try to build overlay if libpciaccess is unavailable.
Date: Wed, 25 May 2016 14:43:59 -0400 [thread overview]
Message-ID: <1464201839-28736-3-git-send-email-robert.foss@collabora.com> (raw)
In-Reply-To: <1464201839-28736-1-git-send-email-robert.foss@collabora.com>
From: Robert Foss <robert.foss@collabora.com>
Don't try to build overlay if libpciaccess is unavailable.
This is useful for platforms that typically don't have pci hardware, like ARM
platforms.
Signed-off-by: Robert Foss <robert.foss@collabora.com>
---
overlay/Makefile.am | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/overlay/Makefile.am b/overlay/Makefile.am
index c926557..a60c6b8 100644
--- a/overlay/Makefile.am
+++ b/overlay/Makefile.am
@@ -1,5 +1,8 @@
+
if BUILD_OVERLAY
-bin_PROGRAMS = intel-gpu-overlay
+ if HAVE_LIBPCIACCESS
+ bin_PROGRAMS = intel-gpu-overlay
+ endif
endif
AM_CPPFLAGS = -I.
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-25 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 18:43 [RFC i-g-t 0/2] Remove build time dependency in libpciaccess robert.foss
2016-05-25 18:43 ` [RFC i-g-t 1/2] configure.ac: Add support for configure flag --disable-pciaccess robert.foss
2016-05-25 18:43 ` robert.foss [this message]
2016-05-25 20:20 ` [RFC i-g-t 2/2] overlay/Makefile: Don't try to build overlay if libpciaccess is unavailable Chris Wilson
2016-05-25 22:07 ` Fwd: " Robert Foss
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=1464201839-28736-3-git-send-email-robert.foss@collabora.com \
--to=robert.foss@collabora.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.stone@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=emil.l.velikov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marius.c.vlad@intel.com \
--cc=tomeu.vizoso@collabora.com \
/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