From: Ricardo Wurmus <rekado@elephly.net>
To: 26356@debbugs.gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>
Subject: bug#26356: [PATCH] gnu: Add intel-gpu-tools.
Date: Tue, 4 Apr 2017 09:15:11 +0200 [thread overview]
Message-ID: <20170404071511.9895-1-rekado@elephly.net> (raw)
* gnu/packages/admin.scm (intel-gpu-tools): New variable.
---
gnu/packages/admin.scm | 53 +++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 52 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/admin.scm b/gnu/packages/admin.scm
index 41b0da4c4..696178a30 100644
--- a/gnu/packages/admin.scm
+++ b/gnu/packages/admin.scm
@@ -8,7 +8,7 @@
;;; Copyright © 2015 Eric Dvorsak <eric@dvorsak.fr>
;;; Copyright © 2016 Leo Famulari <leo@famulari.name>
;;; Copyright © 2016 Pjotr Prins <pjotr.guix@thebird.nl>
-;;; Copyright © 2016 Ricardo Wurmus <rekado@elephly.net>
+;;; Copyright © 2016, 2017 Ricardo Wurmus <rekado@elephly.net>
;;; Copyright © 2016, 2017 Efraim Flashner <efraim@flashner.co.il>
;;; Copyright © 2016 Peter Feigl <peter.feigl@nexoid.at>
;;; Copyright © 2016 John J. Foerch <jjfoerch@earthlink.net>
@@ -67,10 +67,12 @@
#:use-module (gnu packages texinfo)
#:use-module (gnu packages groff)
#:use-module (gnu packages pciutils)
+ #:use-module (gnu packages libunwind)
#:use-module (gnu packages libusb)
#:use-module (gnu packages libftdi)
#:use-module (gnu packages image)
#:use-module (gnu packages xorg)
+ #:use-module (gnu packages xdisorg)
#:use-module (gnu packages python)
#:use-module (gnu packages man)
#:use-module (gnu packages autotools)
@@ -1997,3 +1999,52 @@ with all the commands and parameters identified for your viewing pleasure.
With sedsed you can master any sed script. No more secrets, no more hidden
buffers.")
(license license:expat)))
+
+(define-public intel-gpu-tools
+ (package
+ (name "intel-gpu-tools")
+ (version "1.18")
+ (source
+ (origin (method git-fetch)
+ (uri (git-reference
+ (url "https://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git")
+ (commit (string-append name "-" version))))
+ (sha256
+ (base32
+ "12kigx2k9wpsnzdjrdhwbp1vgiiv2ndrxbs0ll52y51hm0yq0iln"))))
+ (build-system gnu-build-system)
+ (arguments
+ `(#:tests? #f ; many of the tests try to load kernel modules
+ #:phases
+ (modify-phases %standard-phases
+ (add-after 'unpack 'autogen
+ (lambda _
+ ;; Don't run configure in this phase
+ (setenv "NOCONFIGURE" "1")
+ (zero? (system* "sh" "autogen.sh")))))))
+ (inputs
+ `(("util-macros" ,util-macros)
+ ("libdrm" ,libdrm)
+ ("libpciaccess" ,libpciaccess)
+ ("kmod" ,kmod)
+ ("procps" ,procps)
+ ("cairo" ,cairo)
+ ("libunwind" ,libunwind)
+ ("libxrandr" ,libxrandr)
+ ("glib" ,glib)))
+ (native-inputs
+ `(("autoconf" ,autoconf)
+ ("automake" ,automake)
+ ("libtool" ,libtool)
+ ("pkg-config" ,pkg-config)))
+ (home-page "https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/")
+ (synopsis "Tools for development and testing of the Intel DRM driver")
+ (description "Intel GPU Tools is a collection of tools for development and
+testing of the Intel DRM driver. There are many macro-level test suites that
+get used against the driver, including xtest, rendercheck, piglit, and
+oglconform, but failures from those can be difficult to track down to kernel
+changes, and many require complicated build procedures or specific testing
+environments to get useful results. Therefore, Intel GPU Tools includes
+low-level tools and tests specifically for development and testing of the
+Intel DRM Driver.")
+ (license license:expat)))
--
2.12.2
next reply other threads:[~2017-04-04 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 7:15 Ricardo Wurmus [this message]
2017-04-04 15:28 ` bug#26356: [PATCH] gnu: Add intel-gpu-tools Marius Bakke
2017-04-05 20:41 ` Ricardo Wurmus
2017-04-04 20:45 ` Marius Bakke
2017-04-04 21:03 ` Ricardo Wurmus
2017-04-07 21:23 ` Ricardo Wurmus
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=20170404071511.9895-1-rekado@elephly.net \
--to=rekado@elephly.net \
--cc=26356@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.