On Wed, Jul 1, 2009 at 12:51 PM, Pavel Roskin<address@hidden> wrote:
Quoting Bean <address@hidden>:
Perhaps you could also take a look at my previous patch
[PATCH] Use symbol database to maintain module dependence
It add a program grub-symdb to maintain symbol database and therefore
eliminate def- and unf- files, it also allows incremental build.
grub-symdb would need to be compiled by a native C compiler. Otherwise, it
won't work when cross-compiling the utilities.
It's not that it's a big deal per se, but it is will add complexity if we
try to use autoconf to look for it.
Adding grub-symdb to bin_UTILITIES would result in it being installed along
with the utilities that are actually used after the build. I think it's
wrong. Temporary build tools don't belong there.
Hi,
Actually, that's the intention. grub-symdb and the symbol database is
supposed to be installed in the target system. They can be used to
support external grub modules. To install new package, we can just
copy the modules files and use rerun grub-symdb to update the
database.
With the build system, there is a lot of unnecessary rebuilds, as it
relies on a central moddep.lst:
pre-*.o => moddep.lst => mod-*.c => *.mod
As you can see, modification to any source file would cause all the
modules files to be rebuild. Although for most of them, it's only the
trunk, but there is still a lot of necessary work.