linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zebedee Mason <zeb@cyclerouter.co.uk>
To: linux-c-programming@vger.kernel.org
Subject: Dependency analysis
Date: Sun, 26 Jun 2016 22:34:24 +0100 (BST)	[thread overview]
Message-ID: <734731394.6390.64dcef3f-4987-4623-aa6b-0db154f6fc22.open-xchange@email.1and1.co.uk> (raw)
In-Reply-To: <1035222128.24805.b5dc72c3-a052-479c-bfed-f96deb38a264.open-xchange@email.1and1.co.uk>

Hello

I was originally posting to linux-doc, this list seems to be a better fit. So
apologies if you've seen this before.

I've written some software to do dependency analysis. It works by parsing the
output from "make V=1" to extract the relevant include directories before
parsing the source and recursing through the header files. The files are
initially placed in a hierarchy based on the directory structure, obviously the
include directory then causes a circular dependency at a high level so I've
attempted to map the include files into the appropriate source directory. Badly,
as my knowledge of which precise mapping to use is limited.

The html output from Doxygen for the 4.6 kernel is at
http://www.cyclerouter.co.uk/linux/_architecture.html

The source code of the tool is at https://github.com/zebmason/itdepends

The article that accompanies the tool is at
http://www.codeproject.com/Articles/1098935/As-Is-Software-Architecture

HTH

Zeb

           reply	other threads:[~2016-06-26 21:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1035222128.24805.b5dc72c3-a052-479c-bfed-f96deb38a264.open-xchange@email.1and1.co.uk>]

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=734731394.6390.64dcef3f-4987-4623-aa6b-0db154f6fc22.open-xchange@email.1and1.co.uk \
    --to=zeb@cyclerouter.co.uk \
    --cc=linux-c-programming@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).