From: Eric Anholt <eric@anholt.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] gtkdoc: Remove the build_by_default hack
Date: Mon, 04 Jun 2018 14:07:21 -0700 [thread overview]
Message-ID: <87po161cs6.fsf@anholt.net> (raw)
In-Reply-To: <CAKMK7uGDAj+mPskmTOynfbweY9+fGjAGeP2N_hFSm=oHfWibmA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]
Daniel Vetter <daniel.vetter@ffwll.ch> writes:
> On Wed, Apr 4, 2018 at 8:39 PM, Eric Anholt <eric@anholt.net> wrote:
>> Daniel Vetter <daniel.vetter@ffwll.ch> writes:
>>> meson 0.45 properly supports generated content_files. Except for the
>>> minor issue that we're hitting an internal bug in meson. I've made a
>>> pull request for that, but this needs more work:
>>>
>>> https://github.com/mesonbuild/meson/pull/3189
>>>
>>> Downside of this all is that we'd need to up the meson requirements to
>>> something like 0.46, at least if you want to build the docs.
>>
>> What's the status of this? I just pulled this to my vc5 dev branch so
>> that builds don't take ages, and it seems to have fixed it for me.
>
> I need to revise the meson pull to include a proper regression test.
> Which I didn't find time for yet. Then we need to wait until that
> meson is released and in enough distros, and then we can merge this
> patch. As-is, with unpatched meson, this patch breaks the docs build.
Ping - the upstream PR is closed, but I can't tell if 0.46 is usable
yet. I'm still carrying this patch in my trees so I can cross compile.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-06-04 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 14:21 [igt-dev] [PATCH i-g-t] gtkdoc: Remove the build_by_default hack Daniel Vetter
2018-03-06 15:00 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-03-06 20:03 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-04-04 18:39 ` [igt-dev] [PATCH i-g-t] " Eric Anholt
2018-04-05 6:22 ` Daniel Vetter
2018-04-05 8:35 ` Petri Latvala
2018-04-05 9:18 ` Daniel Vetter
2018-04-05 9:28 ` Jani Nikula
2018-06-04 21:07 ` Eric Anholt [this message]
2018-06-18 15:49 ` Daniel Vetter
2018-06-18 16:43 ` Eric Anholt
-- strict thread matches above, loose matches on Subject: below --
2018-06-18 15:49 Daniel Vetter
2018-06-18 15:56 ` Daniel Vetter
2018-06-19 6:41 Daniel Vetter
2018-06-19 6:47 Daniel Vetter
2018-06-20 9:59 ` Petri Latvala
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=87po161cs6.fsf@anholt.net \
--to=eric@anholt.net \
--cc=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