From: Andreas Oberritter <obi@opendreambox.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
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 16:57:33 +0200 [thread overview]
Message-ID: <4F7083DD.8020003@opendreambox.org> (raw)
In-Reply-To: <5951957.sAPiJHEkf3@helios>
On 26.03.2012 16:48, Paul Eggleton wrote:
> On Monday 26 March 2012 16:38:06 Andreas Oberritter wrote:
>> OK, I managed to find a way that's ok for me. I added a wrapper script that
>> wraps the bitbake wrapper script and sets BUILDDIR automatically.
>
> I'm actually working on a couple of fixes that should work for your setup right
> now. If you can wait a little the patches will get posted soon. No additional
> wrapper scripts necessary.
>
>> This way I can als get rid of oe-core/scripts from PATH.
>
> I don't think this is a good idea. If it doesn't cause breakage now I'd be
> surprised if it didn't in the future.
>
>> Can you please ack this patch below, though? This keeps your change intact
>> and surely causes no trouble for you.
>
> This won't be necessary with the fixes I have. The directory where the
> "pseudodone" file is located is supposed to be your build directory, there's no
> need to configure it.
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.
Can you please at least put $BUILDDIR/pseudodone into a variable, so I
can keep my patch small and maintainable?
Regards,
Andreas
next prev parent reply other threads:[~2012-03-26 15:06 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 [this message]
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=4F7083DD.8020003@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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