From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: Achiving My OE environment
Date: Tue, 09 Apr 2013 12:12:09 +0100 [thread overview]
Message-ID: <5163F789.6050700@communistcode.co.uk> (raw)
In-Reply-To: <CAHu+ux0pWKar5pRvsdqkPXq2E2A4+oBRmMqO8W7=h-iX2iKh9w@mail.gmail.com>
On 09/04/13 11:16, 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?
> Thanks
> --
> David Hirst
> hirst689@gmail.com <mailto:hirst689@gmail.com>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
To ensure a fully compatible archive, I do final builds in a virtual
machine and then backup that virtual machine once the build is complete.
This is also a good way to ensure that your layers and everything don't
have local modifications.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2013-04-09 11:29 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
2013-04-09 11:12 ` Jack Mitchell [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=5163F789.6050700@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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