On Fri, Aug 27, 2004 at 11:33:38AM -0500, Timur Tabi wrote:
> I'm working on a driver for the 2.6 Linux kernel, which uses kbuild. I
> don't know if my question is specific to the Linux kernel or kbuild. It
> appears that when I try to compile a driver, my makefile needs to be
> called "Makefile". Is there any way around this? I'd like to have two
> makefiles, "Makefile-2.4" and "Makefile-2.6" and then have a master
> makefile, "Makefile" decide which makefile to use depending on whether
> I'm compiling under a 2.6 kernel or a 2.4 kernel.
There are many different workarounds implemented for this.
None of these were something I really liked - but you find it
in most widely used external modules.
> The problem is that the master kernel makefile appears to have the
> filename "Makefile" hard-coded everywhere. Can this be fixed easily?
> Is there a reason why the filename is restricted?
The Makefile is not really a Makefile - more a kbuild include file.
For that reason I plan to rename it to Kbuild in 2.6 [with support for Makefile].
You cannot 'easily' change this - since this require changing the kernel,
something that is not a possibility for external module.
I recommend to look into some other external module for a good solution.
And then suddenly 2.6 support the Kbuild name.
Sam
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
