public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Anholt <eric@anholt.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 2/3] meson: gtkdoc support
Date: Tue, 6 Mar 2018 14:50:24 +0100	[thread overview]
Message-ID: <20180306135024.GK22212@phenom.ffwll.local> (raw)
In-Reply-To: <871shcr36m.fsf@anholt.net>

On Thu, Feb 22, 2018 at 03:54:09PM -0800, Eric Anholt wrote:
> Daniel Vetter <daniel.vetter@ffwll.ch> writes:
> 
> > Bunch of neat improvements:
> >
> > - xml generates correctly depend upon the test binaries
> > - no need to re-run autogen.sh when new chapters/functions get added,
> >   all handed by meson
> 
> I just rebased on top of this commit, and now my cross build takes 5
> minutes as my skylake build host slowly churns through executing the ARM
> binaries under QEMU.
> 
> Is there anything we could do to avoid executing the built binaries
> during the build process?

meson 0.45 will have the dependency tracking fixed for gtkdoc and will
allow us to drop the always_build hack. I'll see whether we can do a
version check or something like that to work around this all.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-03-06 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 10:16 [PATCH i-g-t 1/3] lib: avoid < in gtkdoc comments Daniel Vetter
2017-12-05 10:16 ` [PATCH i-g-t 2/3] meson: gtkdoc support Daniel Vetter
2018-02-22 23:54   ` Eric Anholt
2018-03-06 13:50     ` Daniel Vetter [this message]
2017-12-05 10:16 ` [PATCH i-g-t 3/3] meson: build a full dependency for lib_igt_perf Daniel Vetter
2017-12-05 10:44   ` Petri Latvala
2017-12-05 11:05     ` Petri Latvala
2017-12-05 11:17 ` ✓ Fi.CI.BAT: success for series starting with [1/3] lib: avoid < in gtkdoc comments Patchwork
2017-12-05 12:17 ` ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2017-12-04 20:48 [PATCH i-g-t 1/3] " Daniel Vetter
2017-12-04 20:48 ` [PATCH i-g-t 2/3] meson: gtkdoc support Daniel Vetter
2017-12-05  9:42   ` 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=20180306135024.GK22212@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=eric@anholt.net \
    --cc=intel-gfx@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