From: Petri Latvala <petri.latvala@intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [igt-dev] [PATCH i-g-t 5/5] docs: Embed subtest descriptions in the documentation
Date: Thu, 20 Jun 2019 15:16:22 +0300 [thread overview]
Message-ID: <20190620121622.GF22949@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190620113819.6pkxoqcgn6e5bdnk@ahiler-desk1.fi.intel.com>
On Thu, Jun 20, 2019 at 02:38:19PM +0300, Arkadiusz Hiler wrote:
> On Thu, Jun 20, 2019 at 02:11:59PM +0300, Petri Latvala wrote:
> > On Thu, Jun 20, 2019 at 01:52:25PM +0300, Arkadiusz Hiler wrote:
> > > On Thu, Jun 20, 2019 at 11:20:18AM +0300, Petri Latvala wrote:
> > > > On Mon, Jun 17, 2019 at 01:54:43PM +0300, Arkadiusz Hiler wrote:
> > > > > This rewrites generate_description_xml in Python, so that we generate
> > > > > properly escaped XML. The switch also makes the code more manageable.
> > > > >
> > > > > Changes in the generated docbook:
> > > > >
> > > > > 1. subtests are not simply listed anymore, they are now another (sub)section
> > > > >
> > > > > 2. subtests are now linkable,
> > > > > e.g. docs/igt-kms-tests.html#kms_hdmi_inject@inject-4k
> > > > >
> > > > > 3. subtest's section now includes output of --describe
> > > > >
> > > > > Python is required already by gtk-doc and we are not using anything
> > > > > other than the standard library.
> > > >
> > > > Python yes, but what about python3? My Debian installation is ancient
> > > > even on Debian standards and gtk-doc-tools depends on python2. I'm too
> > > > lazy to check if the version used by gitlab-CI depends on python3, so
> > > > asking instead: Do you have a fork in gitlab for this? :P
> > >
> > > It works on Fedora:
> > >
> > > % head -n 1 $(which gtkdoc-mkhtml)
> > > #!/usr/bin/python3
> > >
> > > https://gitlab.freedesktop.org/drm/igt-gpu-tools/blob/master/.gitlab-ci.yml#L174
> > >
> > >
> > > But for explicitness I can squash in:
> > >
> > > diff --git a/docs/reference/igt-gpu-tools/meson.build b/docs/reference/igt-gpu-tools/meson.build
> > > index e2bdc495..b3a4c0bd 100644
> > > --- a/docs/reference/igt-gpu-tools/meson.build
> > > +++ b/docs/reference/igt-gpu-tools/meson.build
> > > @@ -45,6 +45,7 @@ test_groups = [
> > > 'vgem',
> > > ]
> > >
> > > +find_program('python3') # required by doc generators
> > > gen_description = find_program('generate_description_xml.py')
> > > gen_programs = find_program('generate_programs_xml.sh')
> >
> >
> > For explicitness I'd prefer something the doc building can depend on
> > to automatically not build them if you don't have python3.
>
> I forgot that we have this weird conditional subdir().
>
> diff --git a/meson.build b/meson.build
> index 6268c58d..1d07af63 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -289,7 +289,8 @@ subdir('overlay')
> subdir('man')
>
> gtk_doc = dependency('gtk-doc', required : build_docs)
> -if build_tests and gtk_doc.found()
> +python3 = find_program('python3', required : build_docs)
> +if build_tests and gtk_doc.found() and python3.found()
> subdir('docs')
> elif build_docs.enabled()
> error('Documentation requires building tests')
LGTM.
Series is
Acked-by: Petri Latvala <petri.latvala@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-20 12:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 10:54 [igt-dev] [PATCH i-g-t 1/5] lib/igt_core: Add support for subtest descriptions Arkadiusz Hiler
2019-06-17 10:54 ` [igt-dev] [PATCH i-g-t 2/5] tests/kms_hdmi_inject: Provide igt_descriptions Arkadiusz Hiler
2019-06-17 12:54 ` Ser, Simon
2019-06-18 10:36 ` [igt-dev] [PATCH v2 " Arkadiusz Hiler
2019-06-19 6:44 ` Ser, Simon
2019-06-17 10:54 ` [igt-dev] [PATCH i-g-t 3/5] tests/kms_plane_multiple: Describe the test Arkadiusz Hiler
2019-06-18 9:36 ` Kahola, Mika
2019-06-17 10:54 ` [igt-dev] [PATCH i-g-t 4/5] CONTRIBUTING: Rework a bit and update Arkadiusz Hiler
2019-06-20 13:49 ` Ser, Simon
2019-06-27 12:57 ` Arkadiusz Hiler
2019-06-27 14:00 ` Ser, Simon
2019-06-17 10:54 ` [igt-dev] [PATCH i-g-t 5/5] docs: Embed subtest descriptions in the documentation Arkadiusz Hiler
2019-06-20 8:20 ` Petri Latvala
2019-06-20 10:52 ` Arkadiusz Hiler
2019-06-20 11:05 ` Ser, Simon
2019-06-20 11:16 ` Arkadiusz Hiler
2019-06-20 11:11 ` Petri Latvala
2019-06-20 11:38 ` Arkadiusz Hiler
2019-06-20 12:16 ` Petri Latvala [this message]
2019-06-24 8:00 ` Ser, Simon
2019-06-27 12:52 ` Arkadiusz Hiler
2019-06-17 13:28 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] lib/igt_core: Add support for subtest descriptions Patchwork
2019-06-17 19:59 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-06-18 12:02 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] lib/igt_core: Add support for subtest descriptions (rev2) Patchwork
2019-06-18 22:45 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-07-01 12:21 [igt-dev] [PATCH i-g-t 1/5] lib/igt_core: Add support for subtest descriptions Arkadiusz Hiler
2019-07-01 12:21 ` [igt-dev] [PATCH i-g-t 5/5] docs: Embed subtest descriptions in the documentation Arkadiusz Hiler
2019-07-03 7:18 ` Ser, Simon
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=20190620121622.GF22949@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=daniel@ffwll.ch \
--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