| Summary: | add Build configuration info to BSP | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexandru Georgescu <alexandru.c.georgescu> |
| Component: | core | Assignee: | Alexandru Georgescu <alexandru.c.georgescu> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bogdanx.a.voiculescu, dvhart, elizabeth.flanagan, meta.mr.watcher, meta.watcher, yp.bsp.watcher, yp.watcher |
| Version: | 1.7 | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexandru Georgescu
2014-03-24 09:48:54 UTC
I don't think we don't want to pollute all our builds with this log file, yes it's good infomration, maybe it could be a summary txt file in the images/<MACHINE> dir instead? This could be handled with an additional bbclass file that is inherited specifically for the autobuilder and installs a task before the final do_build task that writes the data out. Also could you better define the data you are loong for besides the "Build Configuration" from when bitbake starts? We might have to refactor the code in base.bbclass to make it re-usable out side the eventhandler it's currently. We actually have a buildstep that does this already for meta-intel bsps. We can very easily implement this on the ab, so at least the configs are available in the release. I'm gonna move this into work in progress because this depends also on HW automation work that is being done so I will have to wait a little more to fill in the details for it. |