meta-toolchain-gmae should be removed. It's not a GNOME Mobile toolchain because a) GNOME Mobile doesn't exist anymore and b) the libraries in the SDK isn't the complete GNOME Mobile platform, so the chances that it's useful to anyone is pretty slim. Thanks to the "populate_sdk" task everyone can generate a toolchain specifically for their image, and for QA purposes we can just use core-image-sato. So, here's a plan: 1) Add core-image-sato -c populate_sdk to the autobuilder. Note that this is in addition to meta-toolchain-gmae here, not replace. 2) Update QA testcases to use core-image-sato's SDK, not meta-toolchain-gmae 3) Remove meta-toolchain-gmae from autobuilder 4) Remove meta-toolchain-gmae and friends from oe-core.
Hi Ross, There is a command "bitbake meta-toolchain-sdk" to generate the toolchain tarball. Now the meta-toolchain-sdk is equal to meta-toolchain-gmae. If we remove the meta-toolchain-gmae, can we use this command "bitbake meta-toolchain-sdk" instead of "bitbake core-image-sato -c populate_sdk" ? Thanks, Yi
meta-toolchain-sdk is the same as -gmae, so that doesn't actually gain us anything apart from removing the letters "gmae". So no, let's encourage everyone else to use a proper SDK by using a proper SDK ourselves, and use core-image-sato -c populate_sdk.
The populate_sdk task was introduced to remove the need for these "toolchain-sdk" style recipes so removal of this is really a logical conclusion to various developments that have been made.
*Untested* patch for (1) sent.
Patches sent.
Removed from oe-core as of c44fa1206c965054e8e4d316969a8e291cfef590.
Scott says the docs don't mention "gmae" at all.
Hi, I had purged the doc set of this stuff quite some time ago. So it turns out there is no need for a documentation change for this bug. Turning the documentation flag to "No" Scott