On 5/31/07, Arnd Bergmann <[EMAIL PROTECTED]> wrote:
> One way that might be feasible is to have a single header file precompiled,
> and make that include all the common files (fs.h, mm.h, module.h, autoconf.h,
> sched.h, init.h). You then need to pass that header file to gcc as the
> first one that is included, using the '-include' argument.

Agreed, that sounds more correct.

> You also need to take some care about the gcc arguments that you pass.
> E.g. passing -DMODULE when building the precompiled header means that
> you can't use that .pch when you build a file where you don't pass

So does it make sense to build two precompiled headers (one with
CFLAGS_KERNEL, one with CFLAGS_MODULE), and then pass -include
kernel.h.gch and -include module.h.gch for kernel/built-in modules and
loadable modules, respectively? I think I'll try it out and see how it

Thanks. Vegard

This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
kbuild-devel mailing list

Reply via email to