From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp486.redcondor.net (smtp486.redcondor.net [208.80.204.86]) by mail.openembedded.org (Postfix) with ESMTP id 7CF437318A for ; Thu, 25 Aug 2016 14:31:37 +0000 (UTC) Received: from astoria.ccjclearline.com ([64.235.106.9]) by smtp486.redcondor.net ({6695537a-536a-45f9-a249-877c85428649}) via TCP (outbound) with ESMTPS id 20160825143126887_0486; Thu, 25 Aug 2016 14:31:26 +0000 X-RC-FROM: Received: from [216.191.234.70] (port=19506 helo=crashcourse.ca) by astoria.ccjclearline.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1bcvic-00063G-DT; Thu, 25 Aug 2016 10:33:22 -0400 Date: Thu, 25 Aug 2016 10:31:11 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@ca624034.mitel.com To: Javier Viguera In-Reply-To: <47213dd7-8a1a-23a8-68a9-8e7c7452b9f6@digi.com> Message-ID: References: <20160819201637.GO5342@bill-the-cat> <20160821150452.GR5342@bill-the-cat> <47213dd7-8a1a-23a8-68a9-8e7c7452b9f6@digi.com> User-Agent: Alpine 2.20 (LFD 67 2015-01-07) MIME-Version: 1.0 X-MAG-OUTBOUND: ccj.redcondor.net@64.235.106.9/32 Cc: "openembedded-core@lists.openembedded.org" Subject: Re: how can i add u-boot-fw-utils to my build without u-boot being part of the build? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Aug 2016 14:31:40 -0000 Content-Type: text/plain; charset=US-ASCII On Mon, 22 Aug 2016, Javier Viguera wrote: > Hi Robert, > > On 21/08/16 17:51, Robert P. J. Day wrote: > > > > i apologize for being clueless, but i'm still unclear on what i need > > to do here, and in my case, i'm going in the opposite direction. > > > > currently, u-boot is being configured and compiled standalone -- not > > as part of OE. and that build works just fine, so i can grab whatever > > (little?) i need from that build to then add to an actual OE build so > > i can just add u-boot-fw-utils to an existing image. > > > > as i read it, for an OE build of u-boot, i need to supply either > > UBOOT_MACHINE or UBOOT_CONFIG. so in this case, what would i do? my > > assumption until now is that i need to add to the OE build just enough > > to get the fw utils to build, and i'd do that by setting either of > > those variables. and i already have the appropriate fw_env.config file > > ready to go. > > > > so what precisely do i need to do here? > > Have you tried to override UBOOT_CONFIG in a u-boot-fw-utils bbappend? > > Have a look at how we do that (using sandbox_defconfig) in meta-digi-arm: > > https://github.com/digi-embedded/meta-digi/blob/jethro/meta-digi-arm/recipes-bsp/u-boot/u-boot-fw-utils_%25.bbappend ah, this is kind of what i suspected would work ... a generic sandbox build, accompanied by the appropriate /etc/fw_etc.config file. i'm assuming that's not x86-specific since you're using it with one of your ARM boards. thanks, i'll give it a shot. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================