All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Separate build dir for autotools
Date: Mon, 24 Feb 2014 16:27:04 +0000	[thread overview]
Message-ID: <1393259224.31769.15.camel@ted> (raw)
In-Reply-To: <20140224160954.GI26981@jama>

On Mon, 2014-02-24 at 17:09 +0100, Martin Jansa wrote:
> On Mon, Feb 24, 2014 at 03:41:11PM +0000, Burton, Ross wrote:
> > On 24 February 2014 15:27, Martin Jansa <martin.jansa@gmail.com> wrote:
> > > Can we start by adding
> > > include conf/distro/include/seperatebuilddir.inc
> > > to
> > > conf/distro/defaultsetup.conf
> > > ? so that more people start using it and possibly report issues in their
> > > builds?
> > 
> > That list is opt-in and mainly covers oe-core, so this gets tested
> > every time the YP autobuilder does a world build.  We need a meta-oe
> > world build where autotools.bbclass sets B="${WORKDIR}/build": it's
> > literally just this one-line patch.
> 
> But doesn't cover oe-core built with different combinations for
> PACKAGECONFIGs, .bbappends etc, so including this file in
> defaultsetup.conf can still reveal few issues in oe-core recipes.

Patch out for testing, I'll merge it if nobody objects...

Cheers,

Richard




  reply	other threads:[~2014-02-24 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 14:58 RFC: Separate build dir for autotools Richard Purdie
2014-02-24 15:06 ` Otavio Salvador
2014-02-24 15:27 ` Martin Jansa
2014-02-24 15:41   ` Burton, Ross
2014-02-24 16:09     ` Martin Jansa
2014-02-24 16:27       ` Richard Purdie [this message]
2014-02-26 19:11         ` Martin Jansa
2014-02-26 19:54           ` Burton, Ross
2014-02-26 20:20             ` Phil Blundell
2014-02-25 17:36       ` Nicolas Dechesne
2014-02-25 18:43         ` Burton, Ross
2014-02-25 22:10           ` Nicolas Dechesne
2014-02-26 10:58             ` Nicolas Dechesne
2014-02-25  5:46 ` Khem Raj
2014-02-25  9:52   ` Burton, Ross
2014-02-25 16:32     ` 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=1393259224.31769.15.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.