Re: Automatically documenting the architecture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I did receive some feedback and have production hardened my work:
* Revised article -
http://www.codeproject.com/Articles/1098935/As-Is-Software-Architecture
* Revised Linux 4.6 example -
http://www.cyclerouter.co.uk/linux/_architecture.html
* Source code and examples - https://github.com/zebmason/itdepends

The software now 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. In the example the resulting output is then mapped so that the
contents of the include directory are associated with other directories.

Unfortunately my lack of specific kernel knowledge makes this rather a hit and
miss affair. Any comments on how to proceed, or not, as the case may be?

Yours

Zeb
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux