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

[Andre McCurdy]

On Wed, Aug 30, 2017 at 2:03 AM, Tobias Hagelborn
<tobias.hagelborn at axis.com> wrote:
> On 07/07/2017 07:32 AM, Tobias Hagelborn wrote:
>>
>> UPDATE v2:
>> - Rebased on latest Poky
>> - Fixed issue with bad paths
>> - Dirname based on $PN
>>
>> In our organization, there is a demand to be able download source code for
>> searching.
>> With the use of sstate-cache this has been challenge. Also, the source is
>> not gathered
>> but rather spread in a larger directory structure together with build
>> output.
>> There are probably others that also want to be able to do the same.
>>
>> This addition does:
>> * Force download of all source via the srctree_all task
>> * Symlink the source together in a separate directory structure for easier
>> search without
>>    the risk of matching with build output.
>>
>> This is achived with a new class srctree.bbclass that implements the
>> needed tasks and
>> a devtool command srctree which offers a convenience command to set up
>> source for
>> a recipe and it's dependencies.
>>
>> There is also a way of organising the package source code in your own way.
>> This is done by implementing a custom dir generation function and assign
>> to SRCTREE_PN_PATH
>> in a custom class and set SRCTREE_EXTENSION in a configuration file.
>>
>>
>> Tobias Hagelborn (2):
>>    srctree.bbclass: Download sourcecode and make it searchable
>>    devtool: srctree: New command for setting up browsable source-code
>>
>>   meta/classes/srctree.bbclass   | 90
>> ++++++++++++++++++++++++++++++++++++++++++
>>   scripts/lib/devtool/srctree.py | 87
>> ++++++++++++++++++++++++++++++++++++++++
>>   2 files changed, 177 insertions(+)
>>   create mode 100644 meta/classes/srctree.bbclass
>>   create mode 100644 scripts/lib/devtool/srctree.py
>>
>
> Hi
>
> I did not receive any feedback on this one.
>
> We do make good use of this feature and we can't be the only ones who want
> to browse the source of the distro at times?

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


> Cheers
> Tobias
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core