[OE-core] [PATCH v2 0/2] Make source code browsable locally - devtool srctree

Tobias Hagelborn tobias.hagelborn at axis.com
Wed Dec 13 10:32:13 UTC 2017


On 09/05/2017 02:10 PM, Randy MacLeod wrote:
> On 2017-09-01 08:00 AM, Peter Kjellerstedt wrote:
>> Well, the most common request we've gotten from the developers is that
>> they want to be able to search through all the sources, e.g., to find
>> out where a particular function is used. The tmp directory does not
>> lend itself very well to this, given that it also contains all build
>> trees, applied patches and other meta information that bitbake needs.
>> Thus the idea for the parallel tree with only the source references.
>>
>> //Peter
> 
> A shadow tree of links to the source is "mostly harmless" to experts
> and useful for newbies and code browsers as you explained.
> 
> The src dir should be under tmp/src though since anything
> that can be regenerated shouldn't be in the top level
> project directory.

I'll fix that: tmp/srctree

> 
> We don't pay that much (enough?) attention to the SECTION tag
> and something like half of the oe-core recicpes doen't
> have one. I suppose this feature would encourage us to
> fix that.
> 
> Have you run your script with meta-openembedded and other layers?

I've run it with core-image-minimal and core-image-sato.
(I do not think they pull anything in from meta-openembedded)


A new patchset  will soon be available.


//Tobias



More information about the Openembedded-core mailing list