From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] archive.bbclass: archive work directory
Date: Fri, 06 Jan 2012 17:39:57 +0000 [thread overview]
Message-ID: <1325871597.12160.13.camel@phil-desktop> (raw)
In-Reply-To: <b63c8a5a0cf70a797fd49844b7854151a58f579e.1325837822.git.wenzong.fan@windriver.com>
On Fri, 2012-01-06 at 16:20 +0800, wenzong.fan@windriver.com wrote:
> + if [[ -d ${S} && ${S} != ${WORKDIR} ]]; then
> + if [[ ${S} =~ "/work-shared/gcc" ]]; then
> + # Create temporary sources directory for gcc
> + mkdir -p ${PF}/temp
> + cp -r ${S} ${PF}
> + cp -r ${S}/../temp/* ${PF}/temp
> + cp -r ${WORKDIR}/temp/* ${PF}/temp
> + tarbase=`pwd`
Special-casing gcc like this seems a bit lame. Is that check really
needed?
Also, will the above code work with all shells? It looks a bit
bash-specific to me.
p.
next prev parent reply other threads:[~2012-01-06 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 8:20 [PATCH 0/1] archive.bbclass: archive work directory wenzong.fan
2012-01-06 8:20 ` [PATCH 1/1] " wenzong.fan
2012-01-06 8:46 ` Saul Wold
2012-01-09 2:20 ` wenzong fan
2012-01-06 17:39 ` Phil Blundell [this message]
2012-01-09 3:31 ` [PATCH 1/1] archive.bbclass: archive work directoryDistribution wenzong fan
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=1325871597.12160.13.camel@phil-desktop \
--to=philb@gnu.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