From: Tejun Heo <tj@kernel.org>
To: Satish Eerpini <eerpini@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Installer
Date: Mon, 04 Aug 2008 18:25:43 +0900 [thread overview]
Message-ID: <4896CB17.8050701@kernel.org> (raw)
In-Reply-To: <93655eb70808032046y594f38a3u16b7fa2cc6291b1d@mail.gmail.com>
Satish Eerpini wrote:
>> Replacing the normal build output with something different doesn't make
>> anything easier.
>>
>> Especially considering that your "once the .config file is set" seems to
>> assume the user already configured the kernel himself...
>>
>
> i am not just trying to replace the output , i am not a stupid to
> waste my weekend sitting just to replace the output :-),
> if u are interested , u can check out the entire TODO for the app here
> http://satish.playdrupal.com/?q=node/2
>
> but in the process i am stuck at deciding the no of files that will be
> compiled , given that representing the entire compilation
> process as a progress bar , would give a clear idea of " how much is
> over" and "how much is left" !!!
make -n makes make do a dry-run but kbuild is a pretty complex beast and
you might have to jump through some loops to get the information you want.
--
tejun
next prev parent reply other threads:[~2008-08-04 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 20:50 Kernel Installer Satish Eerpini
2008-08-03 21:00 ` Adrian Bunk
[not found] ` <93655eb70808032045vd6130e9m147d3e3ae8b159b5@mail.gmail.com>
2008-08-04 3:46 ` Satish Eerpini
2008-08-04 9:25 ` Tejun Heo [this message]
[not found] ` <93655eb70808040357m2e2893c5n3deb34012d5f212b@mail.gmail.com>
2008-08-04 11:00 ` Satish Eerpini
[not found] ` <12fc08bc0808040658g3fda79a6r407401b2e328ebea@mail.gmail.com>
2008-08-04 21:31 ` Satish Eerpini
2008-08-04 14:03 ` Jeff Dike
2008-08-04 21:30 ` Satish Eerpini
2008-08-04 5:03 ` Bob van Manen
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=4896CB17.8050701@kernel.org \
--to=tj@kernel.org \
--cc=eerpini@gmail.com \
--cc=linux-kernel@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 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.