From: jiangtao.jit@gmail.com (jiangtao.jit)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Is there a tool which can generate a small and simple source tree after config?
Date: Mon, 24 Oct 2011 00:29:36 +0800 [thread overview]
Message-ID: <201110240029342341569@gmail.com> (raw)
Hi:
While reading the kernel code
1. the huge amount of files make me scared
there are too many alike functions in different files
sometimes I can't figure out which one was really compiled
2. too many macros in the definition of a struct or functions declaration
confused me a lot
I tried to follow the generated file autoconf.h to guess the final face
but it's really a difficult thing
Is there a tool which can generate a small and simple source tree after config?
not pre-processor
just generate a small source tree contains the files and dirs which really will be compiled
and no macros like CONFIG_SMP etc.
according to the configuration
or some other way to understand the architecture of the final working source tree?
Thanks.
--
2011-10-23
jiangtao.jit
next reply other threads:[~2011-10-23 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 16:29 jiangtao.jit [this message]
2011-10-23 17:05 ` Is there a tool which can generate a small and simple source tree after config? Aiolia Lea
2011-10-25 2:15 ` Mulyadi Santosa
2011-10-25 7:34 ` Javier Martinez Canillas
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=201110240029342341569@gmail.com \
--to=jiangtao.jit@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.