| Summary: | Produce container image providing extensible SDK | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | devtools / tool chain | Assignee: | Randy Witt <randy.e.witt> |
| Status: | RESOLVED FIXED | QA Contact: | Francisco Pedraza <francisco.j.pedraza.gonzalez> |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | jose.perez.carranza, meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | 2.1 | ||
| Target Milestone: | 2.2 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Paul Eggleton
2016-01-27 03:29:31 UTC
Although this has been done using Dockerfiles, this still needs to be done using oe-core, hence the dependency on 9502. The container image will contain all the host tools needed to use the extensible sdk as well as some helper scripts to "run" the container. Other than that, all other content, oe-core, build output, configuration, etc, will be outside of the container in a workdir that is bind mounted into the container. Currently it is planned to drop the user to a shell to run devtool, but we could just as easily make the container a wrapper around devtool.(which follows the container model more closely) This is finished and exists at https://github.com/crops/extsdk-container |