From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-1.97
Date: Wed, 28 Oct 2009 11:02:00 -0500 [thread overview]
Message-ID: <4AE86AF8.1060000@gmail.com> (raw)
In-Reply-To: <a5d587fb0910280434l2f436fbfo9c6e01f86f0ba57@mail.gmail.com>
Michal Suchanek wrote:
> 2009/10/28 Bruce Dubbs <bruce.dubbs@gmail.com>:
>> I'd also like to make a comment. It may be useful if you split up the build
>> into subdirectories by component. When I extracted the tarball, there were
>> 57 files/directories in the top of the build tree. After configure it was
>> 64. So far so good. However, after make it was over 2400 files, many with
>> very long file names. This makes it almost impossible to navigate form the
>> command line, even on a very big screen. If you split it up, you could also
>> shorten the filenames. I would think that would be an advantage to
>> encourage programmers to read the code and contribute to the project.
>>
>
> I guess it's meant to be used like this:
>
> tar -jxvf grub-version.tar.bz2
> cd grub-version
> mkdir build
> cd build
> ../configure./configure --prefix=/usr \
--sysconfdir=/etc \
--disable-largefile \
--disable-grub-emu \
--disable-grub-emu-usb \
--disable-grub-fstest \
--disable-efiemu --prefix=/some_prefix --options
> make
> make install
Yes, that is exactly what we are doing. Right now the configure line is
./configure --prefix=/usr \
--sysconfdir=/etc \
--disable-largefile \
--disable-grub-emu \
--disable-grub-emu-usb \
--disable-grub-fstest \
--disable-efiemu
> Now you have 2k files in the build directory but the ones that are
> useful can be found under /some_prefix
Right and 1200 of them are *.lst files, many of which have 30+ character
filenames. Doing an ls puts everything in one column. Even if I expand my
terminal to 269 characters, I only get 4 columns of files. It's just hard to
navigate.
> You can find the files installed under /some_prefix in the build
> directory so you can use them directly as well.
Yes, but you have to do `ls -l|grep ^d` just to find out what the directories are.
> Many of the object files are replicated numerous times because of the
> way grub links its modules. This may be addressed at later time, there
> were some patches for simplifying this process.
Since there is only one Makefile, I could take a shot at creating a patch to
address this problem. Would you be interested in such a patch?
-- Bruce
next prev parent reply other threads:[~2009-10-28 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 1:59 grub-1.97 Bruce Dubbs
2009-10-28 9:21 ` grub-1.97 Colin Watson
2009-10-28 15:40 ` grub-1.97 Bruce Dubbs
2009-10-28 11:34 ` grub-1.97 Michal Suchanek
2009-10-28 16:02 ` Bruce Dubbs [this message]
2009-10-28 16:39 ` grub-1.97 Felix Zielcke
2009-10-28 17:23 ` grub-1.97 Felix Zielcke
2009-10-28 17:41 ` grub-1.97 Bruce Dubbs
2009-10-29 3:50 ` grub-1.97 richardvoigt
2009-10-29 4:44 ` grub-1.97 Bruce Dubbs
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=4AE86AF8.1060000@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=grub-devel@gnu.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.