Messages in this thread | | | Date | Thu, 14 Aug 2003 22:31:43 +0200 | From | Sam Ravnborg <> | Subject | Re: C99 Initialisers |
| |
On Thu, Aug 14, 2003 at 12:24:28AM +0200, Roman Zippel wrote: > Something I really want to avoid is Makefile specific syntax in Kconfig. I do not see the point in this. Kconfig should treat this as a block of text - like the help section. Only action to take is to: 1: Find all symbols enclosed in $() a: Check that it exists b: Append CONFIG_
Then Kconfig in each directory should generate a Kconfig.make file, that will be included when kbuild reaches that directory.
> IMO it should somehow like this: > > module maxtorsata MAXTOR_SATA > {tristate|prompt} "SATA for Maxtor IDE" > depends on LIB_SATA > source smaxtor.c > source maxtorlog.c if MAXTOR_VERBOSE
If using the above syntax - where do you see the rules being translated to makefile syntax? kbuild could do this - yes. But I do not see the point in having the extra abstraction layer. Maybe you have something in mind I have not envisioned?
Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |