It seems that the "TOOLCHAIN_TARGET_TASK" is indeed needed to build the mkspecs
but I think that perhaps it should be reworked to only include the Qt modules
used by the image?
> From: [email protected]
> To: [email protected]
> Date: Mon, 7 Dec 2015 06:31:19 +0000
> Subject: Re: [oe] [meta-qt5] Getting Qt support inside an image toolchain
>
> Ok I have solved managed to get this working by adding "inherit populate_sdk
> populate_sdk_qt5" to the top of my image recipe. I just modified the Qt
> recipe to drop "TOOLCHAIN_TARGET_TASK += "packagegroup-qt5-toolchain-target".
> It seems that one needs to inherit "populate_sdk" before "populate_sdk_qt5"
> in order not to invalidate the default TOOLCHAIN_HOST_TASK assignment and
> thereby loose the default SDK components.
>
> I have two questions that arrive though. Firstly, would it be a problem to
> let the Qt recipe inherit from the base one in order to prevent a problem
> like this or could that cause some problems? Also, is it really necessary to
> have "TOOLCHAIN_TARGET_TASK += "packagegroup-qt5-toolchain-target" in the
> recipe? I mean do most users really want to compile every single Qt module
> just to get an SDK?
>
> > From: [email protected]
> > To: [email protected]
> > Date: Sun, 6 Dec 2015 12:03:17 +0000
> > Subject: Re: [oe] [meta-qt5] Getting Qt support inside an image toolchain
> >
> > I have found that adding "inherit populate_sdk_qt5" to my image recipe
> > might be what I need. The problem is that it also fails with building some
> > strange modules. I have found though that this can avoided by removing
> > "nativesdk-packagegroup-qt5-toolchain-host" from that recipe. What seems to
> > have the same effect is to add only "TOOLCHAIN_HOST_TASK +=
> > "nativesdk-packagegroup-qt5-toolchain-host" to my image recipe. This works
> > fine and compiles. It even adds the qt files to the toolchain but for some
> > reason it seems to break the toolchain installer which then crashes with
> > "Setting it up...ls: cannot access /usr/local/simonsdk/environment-setup-*:
> > No such file or directory". This leaves me with a partially installed and
> > useless toolchain. I have looked and looked but I cannot seem to figure out
> > how the qt recipes can be causing this, any ideas?
> >
> > > From: [email protected]
> > > To: [email protected]
> > > Date: Sun, 6 Dec 2015 10:07:26 +0000
> > > Subject: [oe] [meta-qt5] Getting Qt support inside an image toolchain
> > >
> > > I have read that the Qt toolchain components should these days be
> > > included in the toolchain of an image when -c populate_sdk is run for an
> > > image that contains Qt modules. I can confirm that Qt is in fact built
> > > with my image and works on my board. I can also confirm that the
> > > toolchain files like qmake are built and reside in the Yocto build
> > > directories. The problem is that they do not seem to be included in the
> > > toolchain installer. I know one can use meta-toolchain-qt5 but that
> > > appears to want to build every single module there is? Besides wasting a
> > > lot of time and space, that is not really an option for me because the
> > > building of some modules fails because I have a very troublesome bsp that
> > > I have to work with and I do not want to try to fix up those unneeded
> > > packages just to get a toolchain... I know that I have previously been
> > > able to get an sdk built with only the qt modules included in my image
> > > and I could have sworn it was with populate_sdk but that does not seem t
o
> wo
> > rk
> > > now. Is there something that I need to configure before this will work
> > > or is there some other way that it should be built?
> > >
> > > --
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > [email protected]
> > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > [email protected]
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> [email protected]
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
