| Summary: | Include qemu images into sdk tar ball | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | liping Ke <liping.ke> |
| Component: | meta-yocto | Assignee: | Scott Garman <scott.a.garman> |
| Status: | VERIFIED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | jessica.zhang, kevin.tian, lianhao.lu, poky.bs.watcher, poky.watcher, richard.purdie, sgw |
| Version: | 0.9 | ||
| Target Milestone: | 1.0 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
liping Ke
2010-10-14 00:42:44 UTC
Criping, I'm not totally clear on what this involves. Would you want a bootable QEMU kernel and fs image which includes all of the software included in a poky-image-sdk build? Or would you want QEMU images for poky-image-minimal/sato/lsb? Please also suggest a location under the toolchain directory tree where you would like these images kept. With the new installer mechanism, I don't think this requirement is needed anymore since we no longer will have a sdk tar ball... Marking this as OBSOLETE then. Verified obsolete 2010-12-13 |