Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6 V3] Share gcc work directories
Date: Tue, 21 Jun 2011 09:27:29 +0800	[thread overview]
Message-ID: <4DFFF381.7020606@windriver.com> (raw)
In-Reply-To: <BANLkTiknBxHhpfuJJaFkDx83CJamSZr2EQ@mail.gmail.com>



On 06/21/2011 05:01 AM, Khem Raj wrote:
> On Sun, Jun 19, 2011 at 6:48 PM, Robert Yang<liezhi.yang@windriver.com>  wrote:
>>> How does this interact with rm_work?
>>>
>>
>> The rm_work does not delete anything in work-shared, I think this is fine,
>> otherwise the source can not be shared.
>>
>
> it also limits the possibility of patching the sources differently if need be.
> Can it do that easily suppose gcc intermediate needs a patch for a given arch


Yes, the source must be the same if they want to use the shared source. When we
want to patch the source, I think proper way is try to patch them general(not
only for a given arch).

> and others don't then can it make gcc cross intermediate not use shared source

Yes, when the following variables are not defined(or defined to other value)
for gcc intermediate, then it would not use the shared source.


S = "${TMPDIR}/work-shared/gcc-${PV}/gcc-${PV}"
B = "${WORKDIR}/gcc-${PV}/build.${HOST_SYS}.${TARGET_SYS}"

# SS means Shared Stamps directory
SS = "${TMPDIR}/stamps/work-shared/gcc-${PV}"
do_fetch[stamp-base] = "${SS}"
do_unpack[stamp-base] = "${SS}"
do_patch[stamp-base] = "${SS}"

# SW means Shared Work directory
SW = "${TMPDIR}/work-shared/gcc-${PV}"
WORKDIR_task-unpack = "${SW}"
WORKDIR_task-patch = "${SW}"

// Robert

>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



      reply	other threads:[~2011-06-21  1:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 12:41 [PATCH 0/6 V3] Share gcc work directories Robert Yang
2011-06-18 12:41 ` [PATCH 1/6 V3] bitbake: share source directory Robert Yang
2011-06-18 12:41 ` [PATCH 2/6 V3] Share gcc work directories Robert Yang
2011-06-18 12:41 ` [PATCH 3/6 V3] gcc-4.5.1: share " Robert Yang
2011-06-18 12:41 ` [PATCH 4/6 V3] gcc-4.6.0: " Robert Yang
2011-06-18 12:41 ` [PATCH 5/6 V3] gcc-crosssdk: " Robert Yang
2011-06-22 18:55   ` Richard Purdie
2011-06-23  2:01     ` Robert Yang
2011-06-18 12:41 ` [PATCH 6/6 V3] gcc-cross-canadian: " Robert Yang
2011-06-18 12:50 ` [PATCH 0/6 V3] Share gcc " Koen Kooi
2011-06-20  1:48   ` Robert Yang
2011-06-20 21:01     ` Khem Raj
2011-06-21  1:27       ` Robert Yang [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=4DFFF381.7020606@windriver.com \
    --to=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox