On Wed, Sep 9, 2015 at 9:56 PM, Phil Blundell <[email protected]> wrote: > On Wed, 2015-09-09 at 19:34 +1000, Nathan Rossi wrote: >> Note: Only a few different board configurations use CONFIG_FIT_SIGNATURE, >> for 2015.07 this includes "ids8313", "am335x_boneback_vboot" as well as all >> the >> Xilinx Zynq boards. > > Can you make the openssl dependency be a PACKAGECONFIG then (or, even > better, auto-detect it based on the actual configuration in use)? > Dragging it in for everyone doesn't seem all that great if the majority > of users don't actually need the feature.
Auto-detecting would be quite complex as it would need to take into account processing the configs in u-boot before being able to know whether to add the dependency or not. Making this user configurable via PACKAGECONFIG might add additional confusion, especially since it is not a dependency of the target output. Please keep in mind, openssl-native is already dragged in by other dependencies in order to build u-boot (e.g. rpm-native which is added to all recipes inheriting package.bbclass regardless of PACKAGE_CLASSES). Also if you are using u-boot it is likely that you are depending on u-boot-mkimage-native as it is used for kernel image and/or rootfs image packing. Regards, Nathan -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
