From: "Cliff Brake" <cliff.brake@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: oe for two target boards at the same time
Date: Fri, 5 Oct 2007 09:57:44 -0400 [thread overview]
Message-ID: <f96d234e0710050657lbbf7391tb2437588f9c93d31@mail.gmail.com> (raw)
In-Reply-To: <4705D99D.6070209@miromico.ch>
On 10/5/07, Alex <mailinglist@miromico.ch> wrote:
> Hi all
>
> How do I setup my directory structure to use oe for two target boards.
>
> I have an AVR32 board and an AT91 board and would like to use oe for
> both of them with at less dublicated software as possible.
As these are different architectures, I don't think you can use
multimachine. What I typically do is just set up a system where I
share a common overlay (bbcollections), the openembedded directory,
and downloads directory. The nslu2 master makefile what I started
with, but there are other ways. Soft links are used to link the
common directories. EG:
openembedded
openembedded.custom (bb collections overlay)
bitbake
downloads
projectA
openembedded.custom -> ../openembedded.custom
openembedded -> ../openembedded
bitbake -> ../bitbake
downloads -> ../downloads
tmp
conf
projectB
openembedded.custom -> ../openembedded.custom
openembedded -> ../openembedded
bitbake -> ../bitbake
downloads -> ../downloads
tmp
conf
I'd be interested in hearing how others set up their build directory.
Thanks,
Cliff
--
=======================
Cliff Brake
http://bec-systems.com
next prev parent reply other threads:[~2007-10-05 14:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 10:41 hello Tobias Pflug
2007-10-04 11:18 ` hello Michael Krelin
2007-10-04 12:40 ` hello Holger Freyther
2007-10-04 12:55 ` monotone/git (was hello...) Tobias Pflug
2007-10-04 13:27 ` Holger Freyther
2007-10-04 13:50 ` Darcy Watkins
2007-10-04 13:52 ` Michael Krelin
2007-10-05 6:28 ` oe for two target boards at the same time Alex
2007-10-05 13:57 ` Cliff Brake [this message]
2007-10-05 15:47 ` Khem Raj
2007-10-06 8:19 ` Koen Kooi
2007-10-06 11:39 ` Marcin Juszkiewicz
2007-10-08 20:20 ` Cliff Brake
2007-10-09 8:28 ` Koen Kooi
2007-10-09 9:02 ` pHilipp Zabel
2007-10-09 10:36 ` Richard Purdie
2007-10-09 11:18 ` Graeme Gregory
2007-10-09 11:49 ` Graeme Gregory
2007-10-09 16:52 ` Paul Sokolovsky
2007-10-09 16:48 ` Paul Sokolovsky
2007-10-04 18:02 ` monotone/git (was hello...) Richard Purdie
2007-10-04 13:51 ` Michael Krelin
2007-10-04 13:30 ` Michael Krelin
2007-10-04 18:36 ` Chris Larson
2007-10-04 18:49 ` Tim Bird
2007-10-04 18:57 ` Chris Larson
2007-10-04 19:11 ` Michael Krelin
2007-10-04 19:27 ` Chris Larson
2007-10-04 19:39 ` Michael Krelin
2007-10-04 20:18 ` Chris Larson
2007-10-04 20:53 ` Michael Krelin
2007-10-04 19:08 ` Michael Krelin
2007-10-04 19:28 ` Chris Larson
2007-10-04 13:19 ` hello Michael Krelin
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=f96d234e0710050657lbbf7391tb2437588f9c93d31@mail.gmail.com \
--to=cliff.brake@gmail.com \
--cc=openembedded-devel@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 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.