| Summary: | Add automated test for Go toolchain support | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Otavio Salvador <otavio> |
| Component: | devtools / tool chain | Assignee: | Joshua Lock <joshuagloe> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | joshuagloe, meta.mr.watcher, meta.watcher, otavio, ross.burton |
| Version: | 2.4 | ||
| Target Milestone: | 2.4.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | New (Never tested) |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Otavio Salvador
2017-10-02 18:38:06 UTC
Any hints on how to include a go toolchain in your generated SDK?
Is the following conf snippet sufficient?
TOOLCHAIN_HOST_TASK_append = " packagegroup-go-cross-canadian-${MACHINE}"
I added a meta-go-toolchain recipe which has it all. As a learning exercise I implemented a selftest for meta-go-toolchain and an SDK test for an SDK built with Go. I'm not sure both are useful, certainly as the default SDK's don't include Go, so will likely only submit a patch for the former. Patch submitted: https://patchwork.openembedded.org/patch/144674/ |