Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: David Hirst <hirst689@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Achiving My OE environment
Date: Tue, 09 Apr 2013 11:47:45 +0100	[thread overview]
Message-ID: <1365504465.12407.71.camel@ted> (raw)
In-Reply-To: <CAHu+ux0pWKar5pRvsdqkPXq2E2A4+oBRmMqO8W7=h-iX2iKh9w@mail.gmail.com>

On Tue, 2013-04-09 at 06:16 -0400, David Hirst wrote:
> I am trying to achive (svn or tar ball) my whole oe_layersetup
> directory structure.
> However I seem to have problems when I check it out or untar it on a
> different machine.
> It does not seems to build correctly. I set up the paths to the build
> tools and use /conf/setenv
> to set up other paths.
> It seems impossible to build everything correctly without going
> through a comlete installation of the oe-layersetup form the git clone
> and setup script. Does anyone have experiance with this? and have some
> advice?

You need to ensure that:

a) The machine you extract this archive onto has the same distro and
installed package as the one you originally built upon
b) That you extract it to the same path

I would note that:

a) If you don't use the same distro, files can move around, library
versions change and so on. It may work or it may not. We support fresh
builds in this configuration and installs via sstate and some kind of
compatibility matrix but not direct copying.
b) We support relocation of the system using sstate, not by copying.

Cheers,

Richard







  reply	other threads:[~2013-04-09 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 10:16 Achiving My OE environment David Hirst
2013-04-09 10:47 ` Richard Purdie [this message]
2013-04-09 11:12 ` Jack Mitchell

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=1365504465.12407.71.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=hirst689@gmail.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