Posted an alternate patch to bitbake mailing list. -M
On Tue, Mar 7, 2017 at 4:33 PM, Paul Eggleton <[email protected]> wrote: > On Wednesday, 8 March 2017 9:47:23 AM NZDT Richard Purdie wrote: >> On Tue, 2017-03-07 at 13:48 -0600, Matthew McClintock wrote: >> > This is useful in a few scenarios: >> > >> > 1) A developer wants to be able to grep all the code in a particular >> > without having to run patch on various components until they guess >> > the >> > right one (e.g. which component is generating an error/warning?) >> > >> > 2) Other code scanning tools that can be run without requiring a full >> > image to be built (legal, static code analysis, etc) >> > >> > Signed-off-by: Matthew McClintock <[email protected]> >> > --- >> > meta/classes/utility-tasks.bbclass | 7 +++++++ >> > meta/conf/documentation.conf | 1 + >> > 2 files changed, 8 insertions(+) >> >> I have mixed feelings on this. Whilst I can see the attraction, extra >> tasks like this do actually have a parsing overhead. We already have a >> lot of them and its only a question of time before someone wants >> another XXXall task adding. >> >> I'm wondering if we can solve this at the bitbake level instead with a >> new parameter instead? That would allow us to delete tasks and speed up >> parsing rather than slow things down. > > FYI there is a bug open for this (currently assigned to me, but it's in the > "new" state so anyone's welcome to take it): > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=7733 > > I suspect most of this would need to be handled in lib/bb/runqueue.py; > actually adding the option would be in main.py. > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
