| Summary: | Unexpected paths being searched for classes | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | core | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | meta.mr.watcher, meta.watcher |
| Version: | 1.8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2015-01-14 12:08:02 UTC
It turns out there is a reason for this. If for example A.bbclass (in meta/clases) does "inherit B", the system will look for B in "." and "./classes" where "." is the directory containing A.bbclass so you can end up with some bizzare looking path constructs. I'm not sure we can actually do much about this. As previously described, whilst it looks odd, there is a good reason for this. |