From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 15/16] distro: Add separatebuilddir.inc
Date: Thu, 21 Mar 2013 22:00:17 +0000 [thread overview]
Message-ID: <1363903217.16482.148.camel@ted> (raw)
In-Reply-To: <20130321205008.GB3219@jama>
On Thu, 2013-03-21 at 21:50 +0100, Martin Jansa wrote:
> On Thu, Mar 21, 2013 at 03:55:14PM +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
> >
> > diff --git a/meta/conf/distro/defaultsetup.conf b/meta/conf/distro/defaultsetup.conf
> > index be28510..5eb6275 100644
> > --- a/meta/conf/distro/defaultsetup.conf
> > +++ b/meta/conf/distro/defaultsetup.conf
> > @@ -1,6 +1,7 @@
> > include conf/distro/include/default-providers.inc
> > include conf/distro/include/default-versions.inc
> > include conf/distro/include/default-distrovars.inc
> > +include conf/distro/include/seperatebuilddir.inc
>
> Why not add .inc file without including it in defaultsetup.conf so that
> people who want to use it can play with it without influencing others?
This change as it stands should be safe for everyone. My worry is that
people won't test with it and the people using it will have to fix bugs
as they get introduced. If we want to do the opt in approach, we can do
that though (its plan B).
I didn't make the change universally apply since it will break meta-oe
quite badly as things stand today and I know first hand the effort
needed to clean up a batch of recipes.
I should also mention why this is important. With this code enabled, the
build output is cleaned when a package reconfigures so builds become a
bit more stable (e.g. the libpng issue doesn't occur with this applied).
> > include conf/distro/include/world-broken.inc
> >
> > TCMODE ?= "default"
> > diff --git a/meta/conf/distro/include/seperatebuilddir.inc b/meta/conf/distro/include/seperatebuilddir.inc
> > new file mode 100644
> > index 0000000..e1789e0
> > --- /dev/null
> > +++ b/meta/conf/distro/include/seperatebuilddir.inc
> > @@ -0,0 +1,772 @@
> > +# List of autotools recipes which support building with external build directories
> > +# i.e. ${B} != ${S}
> > +SEPB = "${WORKDIR}/build"
> > +
>
> Is there some plan to move this information to recipes? It would be much
> easier to extend this list in layers. Something like set SEPB in recipe
> and then set B = "${SEPB}" in .inc if it's not empty.
That is something we need to think about. I'd really like to make
separate B the default and then add information to the recipes about the
exceptions which don't work. Its going to be a bit of work before we get
there though so this is a stopgap solution.
Cheers,
Richard
next prev parent reply other threads:[~2013-03-21 22:17 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
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 [this message]
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=1363903217.16482.148.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--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.