From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 15/16] distro: Add separatebuilddir.inc
Date: Thu, 21 Mar 2013 17:07:27 +0000 [thread overview]
Message-ID: <1363885647.16482.141.camel@ted> (raw)
In-Reply-To: <1363881315-24352-15-git-send-email-richard.purdie@linuxfoundation.org>
On Thu, 2013-03-21 at 15:55 +0000, Richard Purdie wrote:
> Going forward its going to be useful to separate build data from source data
> in those autotooled projects which support it. Unfortunately there is a lot
> of breakage so for now, this starts the creation of an opt in list which
> we can iterate over enable more recipes over time.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> meta/conf/distro/defaultsetup.conf | 1 +
> meta/conf/distro/include/seperatebuilddir.inc | 772 +++++++++++++++++++++++++
> 2 files changed, 773 insertions(+)
> create mode 100644 meta/conf/distro/include/seperatebuilddir.inc
I should note that when we take this, it will break existing build
directories due to the way autotools handles external builds. I can't
find a good way to avoid this, hence waiting until I'd done a complete
pass over the OE-Core tree before sending it out.
I have tested world builds with this patch applied and either disabled
out of tree builds for broken recipes, or where possible fixed things
up.
Cheers,
Richard
next prev parent reply other threads:[~2013-03-21 17:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 15:55 [PATCH 01/16] libuser: Fix case where ${B} != ${S} Richard Purdie
2013-03-21 15:55 ` [PATCH 02/16] pam: " Richard Purdie
2013-03-21 15:55 ` [PATCH 03/16] watchdog: " Richard Purdie
2013-03-21 15:55 ` [PATCH 04/16] texinfo: " Richard Purdie
2013-03-21 15:55 ` [PATCH 05/16] xinted: " Richard Purdie
2013-03-21 15:55 ` [PATCH 06/16] dpkg: " Richard Purdie
2013-03-21 15:55 ` [PATCH 07/16] python-pygtk: " Richard Purdie
2013-03-21 15:55 ` [PATCH 08/16] rpm: " Richard Purdie
2013-03-21 15:55 ` [PATCH 09/16] pm-utils: " Richard Purdie
2013-03-21 15:55 ` [PATCH 10/16] lzop: " Richard Purdie
2013-03-21 15:55 ` [PATCH 11/16] pth: " Richard Purdie
2013-03-21 15:55 ` [PATCH 12/16] mtdev: " Richard Purdie
2013-03-21 15:55 ` [PATCH 13/16] directfb: " Richard Purdie
2013-03-21 15:55 ` [PATCH 14/16] dhcp: " Richard Purdie
2013-03-21 15:55 ` [PATCH 15/16] distro: Add separatebuilddir.inc Richard Purdie
2013-03-21 17:07 ` Richard Purdie [this message]
2013-03-21 18:30 ` Chris Larson
2013-03-21 22:02 ` Richard Purdie
2013-03-21 20:50 ` Martin Jansa
2013-03-21 22:00 ` Richard Purdie
2013-03-21 22:54 ` Bernhard Reutner-Fischer
2013-03-21 23:21 ` Richard Purdie
2013-03-21 23:53 ` Bernhard Reutner-Fischer
2013-03-21 15:55 ` [PATCH 16/16] scripts/qemu-testlib: Add more debugging information Richard Purdie
2013-03-21 16:30 ` [PATCH 01/16] libuser: Fix case where ${B} != ${S} Burton, Ross
2013-03-23 2:58 ` Khem Raj
2013-03-23 6:46 ` Khem Raj
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=1363885647.16482.141.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.