From: Eric Anholt <eric@anholt.net>
To: Petri Latvala <petri.latvala@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/1] meson: Don't build docs when cross-compiling
Date: Fri, 23 Feb 2018 06:51:58 -0800 [thread overview]
Message-ID: <87zi3zlpwx.fsf@anholt.net> (raw)
In-Reply-To: <20180223111058.30973-1-petri.latvala@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 712 bytes --]
Petri Latvala <petri.latvala@intel.com> writes:
> Building documentation requires executing all test binaries to produce
> their respective description texts. This can be a very time-consuming
> process, if viable at all, when the target arch differs from the
> host.
>
> Don't process the doc directory at all when an exe wrapper is
> setup. This avoids the runtime penalty when the target binaries are
> executed through qemu, but leaves everything as-is when the target
> binaries can be directly executed, like when cross-compiling to x86
> from x86_64 host.
>
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Eric Anholt <eric@anholt.net>
Reviewed-by: Eric Anholt <eric@anholt.net>
Thanks!
[-- 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-02-23 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 11:10 [igt-dev] [PATCH i-g-t 1/1] meson: Don't build docs when cross-compiling Petri Latvala
2018-02-23 12:20 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
2018-02-23 14:51 ` Eric Anholt [this message]
2018-03-06 14:58 ` [igt-dev] [PATCH i-g-t 1/1] " Daniel Vetter
2018-02-23 15:31 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/1] " 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=87zi3zlpwx.fsf@anholt.net \
--to=eric@anholt.net \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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