From: Andre McCurdy <armccurdy@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Tobias Hagelborn <tobiasha@axis.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/2] Make source code browsable locally - devtool srctree
Date: Thu, 31 Aug 2017 13:10:17 -0700 [thread overview]
Message-ID: <CAJ86T=XX0-pkH-4jRMq1o3pJbz-iwGcksGuR7oZHkaYgn86new@mail.gmail.com> (raw)
In-Reply-To: <0fa15a09e9554731a800e4e771e25ab9@XBOX02.axis.com>
On Wed, Aug 30, 2017 at 11:32 PM, Peter Kjellerstedt
<peter.kjellerstedt@axis.com> 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?
next prev parent reply other threads:[~2017-08-31 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 5:32 [PATCH v2 0/2] Make source code browsable locally - devtool srctree Tobias Hagelborn
2017-07-07 5:32 ` [PATCH v2 1/2] srctree.bbclass: Download sourcecode and make it searchable Tobias Hagelborn
2017-07-07 5:32 ` [PATCH v2 2/2] devtool: srctree: New command for setting up browsable source-code Tobias Hagelborn
2017-08-30 9:03 ` [PATCH v2 0/2] Make source code browsable locally - devtool srctree Tobias Hagelborn
2017-08-30 23:16 ` Andre McCurdy
2017-08-31 6:32 ` Peter Kjellerstedt
2017-08-31 20:10 ` Andre McCurdy [this message]
2017-09-01 12:00 ` Peter Kjellerstedt
2017-09-05 12:10 ` Randy MacLeod
2017-12-13 10:32 ` Tobias Hagelborn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ86T=XX0-pkH-4jRMq1o3pJbz-iwGcksGuR7oZHkaYgn86new@mail.gmail.com' \
--to=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=tobiasha@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.