Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@haerwu.biz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: oe for two target boards at the same time
Date: Sat, 6 Oct 2007 13:39:49 +0200	[thread overview]
Message-ID: <200710061339.50324.openembedded@haerwu.biz> (raw)
In-Reply-To: <f96d234e0710050657lbbf7391tb2437588f9c93d31@mail.gmail.com>

Dnia piątek, 5 października 2007, Cliff Brake napisał:
> On 10/5/07, Alex <mailinglist@miromico.ch> wrote:

> > 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.

You can use multimachine even when TARGET_ARCH differ - only *-native 
utils will be the same - all cross tools will be built for both targets.

> What I typically do is just set up a system where I share a common
> overlay (bbcollections), the openembedded directory, 
> and downloads directory.

> I'd be interested in hearing how others set up their build directory.

http://blog.haerwu.biz/2006/11/22/my-openembedded-environment-ii/ is how I 
have it configured.






  parent reply	other threads:[~2007-10-06 11:45 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
2007-10-05 15:47                 ` Khem Raj
2007-10-06  8:19                 ` Koen Kooi
2007-10-06 11:39                 ` Marcin Juszkiewicz [this message]
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=200710061339.50324.openembedded@haerwu.biz \
    --to=openembedded@haerwu.biz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox