From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Andreas Oberritter <obi@opendreambox.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] scripts/bitbake: Allow to override path to pseudodone, make BUILDDIR optional
Date: Mon, 26 Mar 2012 11:07:24 +0100 [thread overview]
Message-ID: <1593126.6uP6AmPbWl@helios> (raw)
In-Reply-To: <4F6CDB0C.6080809@opendreambox.org>
On Friday 23 March 2012 21:20:28 Andreas Oberritter wrote:
> how do you propose to go on solving this problem?
My original patch solved a problem for many newer users who forget to cd back
to their build directories before running bitbake. At least now they get a
reasonable error message they can understand. I'm not going to support
reverting it unless we have a practical alternative and so far I don't see
one.
Your original reason for using the configuration you use was that pseudo was
being rebuilt for every new configuration. I have a fix here locally which will
skip doing this - it just needs to call bitbake -e in order to find out
STAGING_BINDIR_NATIVE if pseudodone hasn't been created.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-26 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 13:37 [PATCH] scripts/bitbake: Allow to override path to pseudodone, make BUILDDIR optional Andreas Oberritter
2012-03-23 20:20 ` Andreas Oberritter
2012-03-26 10:07 ` Paul Eggleton [this message]
2012-03-26 10:29 ` Andreas Oberritter
2012-03-26 14:38 ` Andreas Oberritter
2012-03-26 14:48 ` Paul Eggleton
2012-03-26 14:57 ` Andreas Oberritter
2012-03-26 15:09 ` Paul Eggleton
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=1593126.6uP6AmPbWl@helios \
--to=paul.eggleton@linux.intel.com \
--cc=obi@opendreambox.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.