On 12/14/12 4:12 PM, Tim Bird wrote:
On 12/14/2012 12:45 PM, Mark Hatle wrote:
On 12/14/12 1:46 PM, Burton, Ross wrote:Aha. Thanks very much.
On 14 December 2012 19:43, Tim Bird <tim.bird@...> wrote:I get this question a lot. With the ability (new in 1.3) to build an SDK based
"If you need GMAE, you should use the bitbake meta-toolchain-gmae command. The resulting installation script when run will support such development. However, if you are not concerned with GMAE, youBasically, GMAE means GTK+ 2 and bits of the GNOME stack.
can generate the toolchain installer using bitbake meta-toolchain."
After googling a bit, I figured out that GMAE stands for Gnome Mobile and Embedded.
It might be good to put this acronym somewhere in the manual.
(I'm still not sure if I need GMAE or not...)
A stealth plan of mine is to remove every trace of GMAE from Yocto.
It was an initiative Poky was involved with back in the OpenedHand
days that didn't really take off, and we're still carrying pieces of
on the contents of any arbitrary image.. the meta-toolchain-gmae is simply not
bitbake -c populate_sdk <image recipe>
Is this the preferred way to get a toolchain out of yocto?
That's exactly what I'm working on at the moment (well, after
fixing up some toolchain build issues I've encountered after
messing around a bit with the toolchain recipes...;-)
I don't know if it's the preferred "Yocto Project" way.. but it's the only way I do it.
The code was implemented in the middle of the 1.3 process and does work in 1.3. (However multilib support may not be there. There are a series of patches pending for master that do enable the multilib support as part of the rpm/smart work.)
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
yocto mailing list