From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH i-g-t] lib: Don't use libdrm_nouveau if not found
Date: Mon, 29 Mar 2021 17:07:14 +0300 [thread overview]
Message-ID: <20210329140714.3921-1-petri.latvala@intel.com> (raw)
Only #include the libdrm_nouveau headers if HAVE_LIBDRM_NOUVEAU is set
so IGT builds again without it installed.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Lyude Paul <lyude@redhat.com>
---
lib/igt_nouveau.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lib/igt_nouveau.h b/lib/igt_nouveau.h
index ea44adb2..c518de3c 100644
--- a/lib/igt_nouveau.h
+++ b/lib/igt_nouveau.h
@@ -26,10 +26,6 @@
#include <stddef.h>
#include <inttypes.h>
-#include <nouveau/nouveau.h>
-#include <nouveau/nvif/class.h>
-#include <nouveau/nvif/cl0080.h>
-
#include "igt_core.h"
#define IGT_NOUVEAU_CHIPSET_GV100 0x140
@@ -37,6 +33,10 @@
typedef struct igt_fb igt_fb_t;
#ifdef HAVE_LIBDRM_NOUVEAU
+#include <nouveau/nouveau.h>
+#include <nouveau/nvif/class.h>
+#include <nouveau/nvif/cl0080.h>
+
#define DECL(d) d
#else
/* There shouldn't be any code that calls igt_nouveau_* functions without libdrm support enabled, as
--
2.29.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2021-03-29 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 14:07 Petri Latvala [this message]
2021-03-29 15:03 ` [igt-dev] ✓ Fi.CI.BAT: success for lib: Don't use libdrm_nouveau if not found Patchwork
2021-03-29 16:25 ` [igt-dev] [PATCH i-g-t] " Lyude Paul
2021-03-30 4:05 ` Petri Latvala
2021-03-29 16:52 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
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=20210329140714.3921-1-petri.latvala@intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.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