On Fri, Sep 13, 2013 at 2:58 PM, Hans Beckerus <[email protected]> wrote: > On 2013-09-13 7:32, Otavio Salvador wrote: >> >> On Fri, Sep 13, 2013 at 4:56 AM, Anders Darander <[email protected]> >> wrote: >>> >>> As I've started to bring our internal distro and machines up to the >>> lates oe-core, I've got some issues with the u-boot-fw-utils to >>> u-boot-fw-utils-cross transition. >> >> Right. >> >>> In my old branch, I used u-boot-fw-utils_2011.06. This used to compile >>> and package fw_printenv(setenv) just fine. >>> >>> In the new, u-boot-fw-utils-cross_2013.07.bb, fw_printenv is now built >>> using HOSTCC instead of the cross-compiler. The old recipe used to >>> include: >>> EXTRA_OEMAKE = 'HOSTCC="${CC}"' >>> as u-boot defaults to build everything under tools/ using HOSTC. >> >> Yes; this is intended to be used in the host. I can add support for >> use in target as well (or help you to do it). > > Honestly I do not understand this change at all? fw_printenv typically > *always* executes on the target since it dumps the contents of the U-boot > environment from a shell. Why would you want to build it for the host? That > does not make sense. Unless host is the same as your target which I doubt > could be considered the normal case, or?
It depends on how do you intend to use this. It can be used to mangle environment during image processing. I will cook a patch and send for testing, so we get target ones back. Regards, -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
