On Wed, Aug 30, 2017 at 11:32 PM, Peter Kjellerstedt <[email protected]> wrote: >> >> Just for reference, I think you could achieve something quite similar >> with: >> >> bitbake <your-image> --runall clean ( or rm -rf tmp ) >> bitbake <your-image> --runall patch > > Yes, but the drawback with this is that to find the source code for the > individual packages, you have to dive down into tmp/work/... which can > be quite discouraging for someone who is not an expert in bitbake. What > our developers requested was a way to get easy access to all the source > code being used, typically to be able to search through it all looking > for some specific feature.
Right. I wasn't trying to suggest that the two approaches were completely equivalent, just drawing some attention to the bitbake --runall option, which was added fairly recently (specifically to solve this problem). The directory structure split under tmp/work between arch and machine specific recipes might be a little confusing but obviously serves a purpose (target and native sources may need different sets of patches, etc) so maybe worth the effort to explain to developers. Below that level I don't think there are many surprises in the paths to the sources directories? -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
