| Summary: | Extensible SDK: reparse occurs on first devtool use | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] eSDK | Reporter: | Paul Eggleton <bluelightning> | ||||||
| Component: | eSDK | Assignee: | Paul Eggleton <bluelightning> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | minor | ||||||||
| Priority: | Medium | CC: | jose.perez.carranza, sgw | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 4.99 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||
| Attachments: |
|
||||||||
Created attachment 3994 [details]
Patch to write out contents of hashed config v2
Updated patch attached
So I have a quick fix for this which is to add NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS to BB_HASHCONFIG_WHITELIST; Richard said he thought there was an issue with doing that but he couldn't remember what it was. I think we're going to have to leave this one until 2.5 because fixing it properly is probably too disruptive at this point in the 2.4 cycle. (It's worth noting that fixing this will almost certainly also fix bug 11011 at the same time). This should be fixed by http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f5cd91aae0c0dcd891f07dd6934662ea3a834959 - just need to confirm. I'm going to call this fixed. |
Created attachment 3292 [details] Patch to write out contents of hashed config When you install the eSDK the first step of the build system preparation is of course the usual "parsing recipes". Annoyingly though the first time you run a command that needs to load the cache (e.g. devtool build-image) it parses again from scratch. Using a hack to save the hashed config data out, it seems like it might be related to uninative.