Hi, On Wed, 3 Dec 2008, Sam Ravnborg wrote: > > The config symbol is derived from the module name or can be specified > > after the name. I also added the option to specify the sources, so that > > these can be used to generate the Kbuild information. > > Do you have any idea how do do this properly on the Kbuild side? > I see a few possibilities but have not made up my mind yet. > > 1) We could generate a Kbuild.foo file in the dir where we have the module > 2) We could add info to auto.conf so we could build all modules defined > in the configuration in one step > > Both alternatives have their drawbacks. I'm considering a combination of both. Separate files keeps thing local, as we may need further Makefile fragments, so keeping things local reduces the risk of conflicts. OTOH we should have a global list of all dirs, which is then used by make, this avoids the dependency problem of some old generated Makefile still around which is magically included. > Have you ever considered the possibility to add the Kconfig info > direct in the .c file so we could have a single file driver for the > typical cases? I think currently it would create more problem than it provides in convenience. First you have the dependency problem. How do you find new files? What happens if there are multiple version of a driver (e.g. a backup file). Then there will be a performance problem, so that we would need some caching. Currently the whole Kconfig is read, when something is changed, since it's a only few MB, we get away with with, but if you have to scan all the sources it's a problem. bye, Roman -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
