On Sat, Mar 28, 2009 at 02:36:00PM +0800, Bean wrote: > Hi, > > Currently, the grub-emu is in every rmk files, but I don't see the > difference between grub-emu in i386-pc, i386-coreboot or i386-efi. In > fact, grub-emu runs inside the host os, it can't access firmware > facility anyway. One quick fix to move grub-emu to i386.rmk, but we > could also put it in a new platform altogether, something like > i386-host. > > The advantage of using a separate platform is that we could now use > modules like the other platform, instead of embedding all source files > in grub-emu. For example, whenever we add a new command, we need to > modify the source list of grub-emu. But if we build i386-host like > other platform, we only need to change common.rmk.
Can't we just use common.rmk instead? Adding a separate namespace for util/ stuff looks like unnecessary complication. We already have e.g. grub-probe, grub-setup, etc which don't need this hack. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/grub-devel
