All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	Andre McCurdy <armccurdy@gmail.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: Tue, 5 Sep 2017 08:10:02 -0400	[thread overview]
Message-ID: <90ef5ca5-9697-773a-3281-68a5683cbc95@windriver.com> (raw)
In-Reply-To: <e986d856398445c89fa14558da885793@XBOX02.axis.com>

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.

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?

-- 
# Randy MacLeod.  WR Linux
# Wind River an Intel Company


  reply	other threads:[~2017-09-05 12: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
2017-09-01 12:00         ` Peter Kjellerstedt
2017-09-05 12:10           ` Randy MacLeod [this message]
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=90ef5ca5-9697-773a-3281-68a5683cbc95@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=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.