All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Can't share build trees?
Date: Tue, 03 May 2011 07:31:59 -0600	[thread overview]
Message-ID: <4DC003CF.9010104@mlbassoc.com> (raw)
In-Reply-To: <4DC00309.6040709@mlbassoc.com>

On 05/03/2011 07:28 AM, Gary Thomas wrote:
> On 05/03/2011 07:25 AM, Richard Purdie wrote:
>> On Tue, 2011-05-03 at 05:35 -0600, Gary Thomas wrote:
>>> I have a system which has both PowerPC and ARM/OMAP components.
>>> They share a common Poky/Yocto layer, so I thought I'd be able
>>> to also share a build tree. So, I tried something like this:
>>> % . /opt/poky/oe-init-build-env my_target
>>> % MACHINE=MY_OMAP bitbake omap-image
>>> % MACHINE=MY_PPC bitbake ppc-image
>>>
>>> All seemed fine the first time through. The images were built
>>> as expected and worked well.
>>>
>>> Sadly, when I tried to build something else, e.g.
>>> % MACHINE=MY_OMAP bitbake some-package
>>> it set off rebuilding the entire cross tool chain :-(
>>>
>>> Should this work? or should I just be aware it does not (and mostly
>>> tell my customers not to expect it to work)?
>>
>> It should work and its the way I use Poky. Did you update the metadata
>> between these builds changing the toolchain version for example (e.g.
>> gcc 4.6.0 testing)?
>
> No changes, just changed the MACHINE

I'll try it again, just to make sure I can duplicate it.

I'm happy to hear that this should work.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2011-05-03 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 11:35 Can't share build trees? Gary Thomas
2011-05-03 13:25 ` Richard Purdie
2011-05-03 13:28   ` Gary Thomas
2011-05-03 13:31     ` Gary Thomas [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=4DC003CF.9010104@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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.