| Summary: | Extensible SDK: ability to install needed development libraries and headers from published package feeds. | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexander Kanevskiy <alexander.kanevskiy> |
| Component: | devtools / tool chain | Assignee: | Paul Eggleton <bluelightning> |
| Status: | VERIFIED FIXED | QA Contact: | Daniel Istrate <daniel.alexandrux.istrate> |
| Severity: | enhancement | ||
| Priority: | High | CC: | alexandru.c.georgescu, bogdanx.a.voiculescu, markus.lehtonen, meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | 1.9 | ||
| Target Milestone: | 2.0 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Alexander Kanevskiy
2015-08-10 14:29:04 UTC
The dilemma here is whether we can use sstate in this process or we just have the package feeds? For various reasons the project has been tending toward using sstate rather than the package feeds directk. sstate is possibility, but wouldn't solve ability to install build dependencies from custom user repositories. E.g. 3rd party software vendor to provide their own framework addons on top of main distro. So we've implemented the basic functionality using devtool and sstate; without using package feeds directly. I'm therefore marking this as resolved for 2.0 and we can open new bugs for additional functionality as needed. devtool and sstate does the job. |