From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1Qcgsk-00017a-GZ for bitbake-devel@lists.openembedded.org; Fri, 01 Jul 2011 18:47:54 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p61FmHmk012409; Fri, 1 Jul 2011 16:48:17 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12158-05; Fri, 1 Jul 2011 16:48:13 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p61Fm9Lw012403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jul 2011 16:48:10 +0100 From: Richard Purdie To: Joshua Lock In-Reply-To: References: Date: Fri, 01 Jul 2011 16:47:47 +0100 Message-ID: <1309535267.20015.523.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Virus-Scanned: amavisd-new at rpsys.net Cc: bitbake-devel@lists.openembedded.org Subject: Re: [PATCH 00/10] Hob - BitBake GUI X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 16:47:54 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2011-06-30 at 23:02 -0700, Joshua Lock wrote: > Of course, before sending this pull request I ran some final tests and > encountered a significant problem with the implementation approach. > Images are built by first using the buildTargets command to build all of the > target dependencies then creating a recipe file and using the buildFile > command to handle the build. > The problem is that if you have a clean build directory, perfectly reasonable > with such a tool, the buildFile command does not handle the native > dependencies added by the image class. > > The alternative I have is to save the image files somewhere within BBPATH, > and perhaps suggest the user create a "workspace" layer, and build them with > buildTargets. I didn't do this because I'd rather not pollute the users file > system without good cause. It may be the only tenable approach though. > > Any suggestions here? I think you should be able to modify the base configuration data and just add a local directory that the image creator uses to BBPATH yourself? That way you should always be able to use buildTargets... Cheers, Richard