From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [68.230.241.39] (helo=fed1rmmtao107.cox.net) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1LO1R7-0007rj-81 for openembedded-devel@openembedded.org; Sat, 17 Jan 2009 04:01:25 +0100 Received: from fed1rmimpo03.cox.net ([70.169.32.75]) by fed1rmmtao107.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090117025435.IEUO131.fed1rmmtao107.cox.net@fed1rmimpo03.cox.net> for ; Fri, 16 Jan 2009 21:54:35 -0500 Received: from localhost ([68.230.61.57]) by fed1rmimpo03.cox.net with bizsmtp id 4Sua1b0021E665w04SuaUR; Fri, 16 Jan 2009 21:54:36 -0500 X-Authority-Analysis: v=1.0 c=1 a=LLvST7gcIdsA:10 a=0G8rmy93P40A:10 a=b2ZvGRdsAAAA:8 a=33fAdri4_T977m9DqH8A:9 a=ytdNhe4rCkKUOpU4vgtZRb0haigA:4 a=LY0hPdMaydYA:10 X-CM-Score: 0.00 Date: Fri, 16 Jan 2009 19:54:34 -0700 From: Tom Rini To: openembedded-devel@openembedded.org Message-ID: <20090117025434.GS6710@smtp.west.cox.net> References: <1230827114.5320.42.camel@dax.rpnet.com> <20090101182526.GF7040@smtp.west.cox.net> <1230840687.5320.56.camel@dax.rpnet.com> <20090101220229.GH7040@smtp.west.cox.net> <1230858713.10424.4.camel@dax.rpnet.com> <1231462490.6467.85.camel@dax.rpnet.com> <20090114011539.GA2376@smtp.west.cox.net> <20090114231705.GG6710@smtp.west.cox.net> MIME-Version: 1.0 In-Reply-To: <20090114231705.GG6710@smtp.west.cox.net> Organization: Embedded Alley Solutions, Inc User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: RFC: "Virtual" native and sdk recipes X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 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: Sat, 17 Jan 2009 03:01:25 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 14, 2009 at 04:17:05PM -0700, Tom Rini wrote: > On Tue, Jan 13, 2009 at 06:15:39PM -0700, Tom Rini wrote: > > On Fri, Jan 09, 2009 at 12:54:50AM +0000, Richard Purdie wrote: > > > On Fri, 2009-01-02 at 01:11 +0000, Richard Purdie wrote: > > > > I just had a look through the trini/canadian-sdk branch and there are > > > > bits I like and bits I dislike. I'll try and provide some feedback in > > > > due course with a view to getting the less controversial bits merged. I > > > > have some tweaks in poky to do with dynamic library extension handling > > > > for example (from playing with darwin targets) where it would pay us to > > > > find a common solution. > > > > > > Sorry for the delayed feedback, what I've looked at so far follows > > > below. It was easiest to extract some patches from your tree and make > > > some commits of my own so these are in: > > > > > > http://git.openembedded.net/?p=openembedded.git;a=shortlog;h=refs/heads/rpurdie/canadian-sofar > > > > > > Basically I wanted to particularly review the changes to the existing OE > > > core classes/bitbake.conf. The changes in that branch are versions I'm > > > happy with. I had two concerns there: > > > > > > 1. I don't want to see ${HOST_EXEEXT} everywhere but I know why you > > > need it and this was something OE would inevitably face. As a > > > compromise I propose adding: > > > > > > EXEEXT = "${HOST_EXEEXT}" > > > > > > and using ${EXEEXT} which is fractionally less ugly for all common > > > uses. Could you update your patch to use ${EXEEXT} please assuming > > > we all agree on this. Its the same dilemma as the SOLIBS stuff I > > > have with Darwin :/ > > > > > > 2. All the bb.data.inherits_class() stuff is ugly as sin and totally > > > unreadable. My series has a better patch. > > > > > > Moving on to the rest of the code, I don't see a problem merging any of > > > the totally new files. How about the following merge process: > > > > > > a) We push my tree into OE > > > > My git-fu is weak and since we can't delete remote branches without > > bugging someone, can we do this step? I've got... > > > > > b) You rebase onto my tree's changes and adjust the EXEEXT stuff. > > > > > > c) You add changes which add the EXEEXT changes only to existing > > > recipes and commit that. > > > > > > d) The checksums.ini changes are a no brainer. > > > > > > e) You start adding the totally new files to OE directly in a logical > > > sequence of something like: > > > > > > i) Add canadian core classes (classes/canadian*) > > > ii) Add mingw new recipes > > > iii) Add misc support recipes (gmp/mprf-canadian) > > > iv) Add new binutils recipes > > > v) Add new gcc recipes > > > > ... this done locally, mostly, in quilt. > > Making more noise as I'm thinking on Friday I'll just merge RP's branch > to mainline. I'm fairly certian my git-fu did not fail and this has been done. I'll make branch of e-i -> e-v soon I hope (painting in the new house this weekend). -- Tom Rini