On Wed, Oct 19, 2016 at 08:00:12PM -0700, Khem Raj wrote: > > > On Oct 19, 2016, at 1:19 AM, thilo.ceston...@ts.fujitsu.com wrote: > > > > Hey! > > > > I want to create such a nice toolchain installation package for my image > > recipe. > > The problem I currently hit is, that I need to do populate_sdk and > > populate_sdk_qt5 to have qt5 toolchain too. > > > > Now I had an idea to create a recipe for the SDK like: > > > > ---------- > > SUMMARY = "Meta package for building an installable toolchain" > > LICENSE = "MIT" > > > > PR = "r0" > > > > inherit populate_sdk populate_sdk_qt5 > > ————— > > > what is the advantage of such a recipe?
I guess the question is more generic... The advantages of a separate meta-toolchain* recipe: * a lot of flexibility * not tied to a specific image * can carry a lot of SDK customizations > > But how can I tell the recipe to additionally install all the "*-dev" > > packages which my original image recipe installs. > > When I require the image recipe, the toolchain recipe does a do_rootfs task > > (which is not needed, as it is done by building the image). > > > > I read something about TOOLCHAIN_TARGET_TASK and adding all the "*-dev" > > packages I want to this. But that doesn't work. > > > > Any hints? > > > > cheers, > > Thilo-- > > _______________________________________________ > > Openembedded-core mailing list > > Openembedded-core@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core