| Summary: | Add runtime dependencies for native "packages" | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | core | Assignee: | Richard Purdie <richard.purdie> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher |
| Version: | 2.2 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Ross Burton
2016-10-13 15:48:52 UTC
The question is how exactly? Its very hard to tell whether a recipe requires X at runtime or buildtime given our current dependency markup since most things just get added to DEPENDS. A whitelist of "build tools"? Moving to future until someone comes up with a proposal we could implement... http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/layer.conf now sets SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS which excludes git-native, quilt-native and so on and SSTATE_EXCLUDEDEPS_SYSROOT += ".*->bison-native" to exclude bison-native. We probably need to extend the latter to include other things like autoconf.native? We stopped clearing PACKAGES in native.bbclass which was progress Bulk move from 4.99 or 0.00 to 5.99 |