| Summary: | Remove meta-toolchain-gmae | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | devtools / tool chain | Assignee: | Ross Burton <ross.burton> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | elizabeth.flanagan, meta.mr.watcher, meta.watcher, richard.purdie, sgw, srifenbark, yi.zhao |
| Version: | 1.4 | ||
| Target Milestone: | 1.6 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | 21 March 2014: Reset documentation flag to "No" | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2013-06-26 11:16:34 UTC
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 |