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? For reference the U-Boot makefile setup handles the dependence on the tools, and will ensure they are built before needed. So splitting out the steps is probably not necessary. Regards, Nathan -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
