From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Andreas Oberritter <obi@opendreambox.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] scripts/bitbake: Allow to override path to pseudodone, make BUILDDIR optional
Date: Mon, 26 Mar 2012 16:09:09 +0100 [thread overview]
Message-ID: <1380334.QcVfQnLvhe@helios> (raw)
In-Reply-To: <4F7083DD.8020003@opendreambox.org>
On Monday 26 March 2012 16:57:33 Andreas Oberritter wrote:
> I'm not convinced. If I delete tmp, pseudo gets deleted, but pseudodone
> stays. In my opinion, pseudodone's intuitive location is tmp, if the
> location of tmp is known - which it is in my case.
pseudodone exists so that the script does not have to ask bitbake every time
it is run where to find the pseudo executable (i.e., STAGING_BINDIR_NATIVE).
Now, at the moment the script is lazy and assumes if the file doesn't exist
then it needs to build pseudo even if that isn't needed. I have a fix for this
already, so this problem is taken care of.
> Can you please at least put $BUILDDIR/pseudodone into a variable, so I
> can keep my patch small and maintainable?
If the above is fixed and you can move freely between build directories without
re-running a setup script, then unless I'm mistaken your immediate problems
have now been addressed...?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-03-26 15:18 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
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 [this message]
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=1380334.QcVfQnLvhe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox