From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [64.233.162.237] (helo=nz-out-0506.google.com) by linuxtogo.org with esmtp (Exim 4.67) (envelope-from ) id 1IdpTm-0000Xs-Sf for openembedded-devel@lists.openembedded.org; Fri, 05 Oct 2007 17:52:43 +0200 Received: by nz-out-0506.google.com with SMTP id i11so435592nzh for ; Fri, 05 Oct 2007 08:47:17 -0700 (PDT) Received: by 10.115.23.12 with SMTP id a12mr2779972waj.1191599235249; Fri, 05 Oct 2007 08:47:15 -0700 (PDT) Received: by 10.114.208.4 with HTTP; Fri, 5 Oct 2007 08:47:15 -0700 (PDT) Message-ID: <19c1b8a90710050847o4a3dff07na8f0f18baaf56bcf@mail.gmail.com> Date: Fri, 5 Oct 2007 08:47:15 -0700 From: "Khem Raj" To: openembedded-devel@lists.openembedded.org In-Reply-To: MIME-Version: 1.0 References: <1191494488.2516.34.camel@toontown> <4704CC05.40206@klever.net> <1191502502.2516.39.camel@toontown> <4704F01B.70104@klever.net> <4705D99D.6070209@miromico.ch> Subject: Re: oe for two target boards at the same time X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2007 15:52:43 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I generally use a separate tmp directory for each machine and common sources. This has worked well for me so far. -Khem On 10/5/07, Cliff Brake wrote: > On 10/5/07, Alex 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 > > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel >