hum, how about doxygen?<div><br><div class="gmail_quote">On Sun, Oct 23, 2011 at 6:29 PM, jiangtao.jit <span dir="ltr"><<a href="mailto:jiangtao.jit@gmail.com">jiangtao.jit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi:<br>
<br>
While reading the kernel code<br>
1. the huge amount of files make me scared<br>
there are too many alike functions in different files<br>
sometimes I can't figure out which one was really compiled<br>
2. too many macros in the definition of a struct or functions declaration<br>
confused me a lot<br>
I tried to follow the generated file autoconf.h to guess the final face<br>
but it's really a difficult thing<br>
<br>
Is there a tool which can generate a small and simple source tree after config?<br>
not pre-processor<br>
just generate a small source tree contains the files and dirs which really will be compiled<br>
and no macros like CONFIG_SMP etc.<br>
according to the configuration<br>
<br>
or some other way to understand the architecture of the final working source tree?<br>
<br>
Thanks.<br>
<font color="#888888"><br>
--<br>
2011-10-23<br>
jiangtao.jit<br>
<br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</font></blockquote></div><br><br clear="all"><div><br></div>-- <br>Best Regards!<br>Aiolia Lea<br><br>
</div>