Hey > Well, have your image `inherit populate_sdk_qt5`, and then call > > `bitbake <your-image> -c populate_sdk`. That'll give you the standard, > image-based SDK, with Qt5 in it. > Can the image and the sdk be build seperatly then? Or will a "bitbake <my-image>" build the qt5 toolchain directly too? This is what I intended to get rid off. To be able to build the image and the sdk in two independed build steps.
Cheers, Thilo
smime.p7s
Description: S/MIME cryptographic signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
