From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: IGT development <igt-dev@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: [igt-dev] [PATCH i-g-t 1/2] README: Use meson for building docs
Date: Thu, 13 Dec 2018 13:43:54 +0100 [thread overview]
Message-ID: <20181213124355.1420-1-daniel.vetter@ffwll.ch> (raw)
Also simplify the instructions for meson 0.47+, where we track
dependencies correctly.
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
README.md | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index dcff03efdbac..f09e10f77f41 100644
--- a/README.md
+++ b/README.md
@@ -126,7 +126,7 @@ to generate this API documentation.
To regenerate the html files when updating documentation, use:
- $ make clean -C docs && make -C docs
+ $ ninja -C build igt-gpu-tools-doc
If you've added/changed/removed a symbol or anything else that changes
the overall structure or indexes, this needs to be reflected in
@@ -188,14 +188,19 @@ Note that meson insist on separate build directories from the source tree.
Running selfchecks for lib/tests and tests/ is done with
- $ cd build && ninja test
+ $ ninja -C build test
Note that this doesn't actually run the testcases in tests/: scripts/run-tests.sh
should continue to be used for that.
Documentation is built using
- $ cd build && ninja && ninja igt-gpu-tools-doc
+ $ ninja -C build igt-gpu-tools-doc
+
+Note that this needs meson v0.47 or later, earlier versions of meson do not
+track depencies correctly for the codumentation build and need:
+
+ $ ninja -C build && ninja -C build igt-gpu-tools-doc
Note that there's a setup script similar to ./autogen.sh which creates a
compatibility Makefile with a few useful default targets:
--
2.20.0.rc1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-12-13 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 12:43 Daniel Vetter [this message]
2018-12-13 12:43 ` [igt-dev] [PATCH i-g-t 2/2] autoconf: Drop gtkdoc support Daniel Vetter
2018-12-13 13:08 ` Petri Latvala
2018-12-13 15:46 ` Daniel Vetter
2018-12-13 13:05 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] README: Use meson for building docs Patchwork
2018-12-13 13:06 ` [igt-dev] [PATCH i-g-t 1/2] " Petri Latvala
2018-12-13 16:02 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2] " 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=20181213124355.1420-1-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@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