| Summary: | Sanity check SDK_VENDOR | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | devtools / tool chain | Assignee: | Ankur Tyagi <ankur.tyagi85> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | ankur.tyagi85, meta.mr.watcher, meta.watcher, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 3.1 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | NEWCOMER BACKPORT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2019-10-04 15:50:13 UTC
I thought of putting a check inside sdk_variables() inside populate_sdk_base class but it has limitations: - works only for the first time but not for successive invoke - only works for populate_sdk but misses meta-toolchain Can I get some more insight/ideas on this? thanks A better place to do that logic would be sanity.bbclass, this is where all of the pre-build sanity checks are implemented. Hi Ross, This seems to be fixed now by your commit https://github.com/openembedded/openembedded-core/commit/b0efd8d4d0dbc30e6505b42f5603f18fa764d732 This bug can be closed Huh. I had totally forgotten I wrote that. Sorry for not closing this earlier. |