On Thu, Aug 25, 2016 at 10:00:20AM +0200, Johannes Berg wrote: > > > The other nice thing is that we could probably fold most of the > > Makefiles into Kconfig using that methods as well, by listing the > > objectes required for a module, e.g. > > > > module NVME_TARGET > > tristate "NVMe Target support" > > depends on BLOCK > > depends on CONFIGFS_FS > > name nvmet > > objects core.o configfs.o admin-cmd.o io-cmd.o fabrics-cmd.o > > objects discovery.o > > > > If this was going to be a thing, then you might also have > > config NVME_TARGET_FOO > bool "NVMe target supports FOO" > module NVME_TARGET > objects foo.o You mean this instead of a Makefile: foo-$(CONFIG_NVME_TARGET_FOO) += foo.o ? > The "module" would be like a "depends on" plus giving the module for > generating the Makefile, and now you can really remove most Makefile > stuff... :) Luis -- To unsubscribe from this list: send the line "unsubscribe backports" in
