| Summary: | Add documentation about what each generic task does in Yocto | ||
|---|---|---|---|
| Product: | [Documentation] Reference | Reporter: | Stoicescu Cornel <corneliux.stoicescu> |
| Component: | handbook | Assignee: | Scott Rifenbark <srifenbark> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, dvhart, poky.doc.watcher, poky.watcher |
| Version: | 1.6 | ||
| Target Milestone: | 1.6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 31 October 2013: RESOLVED | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Done (doc changes complete) | |
|
Description
Stoicescu Cornel
2013-10-04 09:03:42 UTC
This should mostly be covered by the newly added "A Closer Look at the Yocto Project Development Environment" section of the reference manual; at least it does mention the task names in each section covering the related conceptual step of the build process. I agree. I think that new chapter in the reference manual covers this information. Look at http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#closer-look and see if this is adequate to cover this bug. BTW - this section will continue to evolve. Scott I am marking this RESOLVED since there has been no feedback against it. The 'Bitbake' subsection from the 'A closer look' section does cover my request. Marking it as VERIFIED. |