| Summary: | Incorrect runall fetch command example in the development manual | ||
|---|---|---|---|
| Product: | [Documentation] Development Manual | Reporter: | Ahmed Hossam <Ahmed.Hossam> |
| Component: | development | Assignee: | Mark Morton <mark.morton> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | akuster808, akuster, randy.macleod, richard.purdie |
| Version: | 2.6.4 | ||
| Target Milestone: | 3.1 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Ahmed Hossam
2019-12-19 15:36:25 UTC
Ping. M3 is in 2 weeks. Got it - thanks for the reminder. I sent a patch for this and queued in master-next Is the '-c' needed (I have not tested that) ? I have tried the command and if I understand correctly -c interprets 'target' as a command so bitbake assumes that no target is passed and just prints a help message: $ bitbake -c target --runall="fetch" Nothing to do. Use 'bitbake world' to build everything, or run 'bitbake --help' for usage information. You are correct, the -c should not be there either. I've fixed the patch queued in master-next to remove that. |