On Mon, Sep 14, 2015 at 9:05 AM, Nathan Rossi <[email protected]> wrote: > On Mon, Sep 14, 2015 at 9:49 PM, Otavio Salvador > <[email protected]> wrote: >> On Mon, Sep 14, 2015 at 6:29 AM, Nathan Rossi <[email protected]> wrote: >>> On Fri, Sep 11, 2015 at 3:50 AM, Otavio Salvador >>> <[email protected]> wrote: >>>> On Thu, Sep 10, 2015 at 7:24 AM, Nathan Rossi <[email protected]> >>>> wrote: >>>>> U-Boot will compile its own tools during the build, with specific >>>>> configurations (aka when CONFIG_FIT_SIGNATURE is enabled) the host tools >>>>> require openssl. This patch adds 'openssl' as a PACKAGECONFIG that >>>>> enables the use of openssl-native as a dependency and also adds the >>>>> HOSTCC flags that U-Boot uses when compiling the host tools. >>>>> >>>>> Signed-off-by: Nathan Rossi <[email protected]> >>>> >>>> Ideally we ought to ensure U-Boot stops to build the native part when >>>> doing the target one. >>> >>> Are you suggesting that the compile step (of the recipe) should build >>> the "tools"/native make target first, then execute the make target for >>> the rest afterwards as two separate steps? >> >> Two separated _recipes_. > > Ah ok, to some degree that already exists with the u-boot-mkimage and > u-boot-fw-utils recipes. However the problem is that there is > currently no easy way (at least with mainline U-Boot) to get U-Boot to > use the tools provided by the host/sysroot/PATH instead of building > them.
I know but this seems to be the route we ought to pursuit. -- 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
