From: Easwar Hariharan via igt-dev <igt-dev@lists.freedesktop.org>
To: igt-dev@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [igt-dev] [PATCH i-g-t v2] README: Add pointer to Dockerfiles for easy lookup of dependencies
Date: Wed, 13 Feb 2019 09:43:58 -0800 [thread overview]
Message-ID: <20190213174358.131146-1-easwar.hariharan@intel.com> (raw)
I spent quite some time trying to install all the dependencies to build
igt in for my distribution. After installing the packages, I noticed
that the Dockerfiles had the exact packages required for each
distribution. Add a pointer to the Dockerfiles in the README to save
folks time on setting up the environment required to build igt.
CC: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Easwar Hariharan <easwar.hariharan@intel.com>
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index eebed07b..2d583095 100644
--- a/README.md
+++ b/README.md
@@ -176,6 +176,8 @@ The following dependencies are requires for building audio support
libasound2-dev
libgsl-dev
+See Dockerfiles.* for package names in different distributions.
+
Meson build system support
--------------------------
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-02-13 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 17:43 Easwar Hariharan via igt-dev [this message]
2019-02-13 17:52 ` [igt-dev] [PATCH i-g-t v2] README: Add pointer to Dockerfiles for easy lookup of dependencies Rodrigo Vivi via igt-dev
2019-02-13 17:57 ` Rodrigo Vivi via igt-dev
2019-02-13 18:15 ` Hariharan, Easwar via igt-dev
2019-02-13 18:09 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-02-14 10:56 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190213174358.131146-1-easwar.hariharan@intel.com \
--to=igt-dev@lists.freedesktop.org \
--cc=easwar.hariharan@intel.com \
--cc=rodrigo.vivi@intel.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