From: Roman Zippel <zippel@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Subject: Re: distributed module configuration [Was: Announce: Linux-next (Or Andrew's dream :-))]
Date: Thu, 14 Feb 2008 01:56:13 +0100
User-Agent: KMail/1.9.7
Cc: David Miller <davem@davemloft.net>, greg@kroah.com,
       torvalds@linux-foundation.org, jeff@garzik.org, arjan@infradead.org,
       sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
       linux-next@vger.kernel.org, linux-arch@vger.kernel.org,
       akpm@linux-foundation.org, linux-kbuild <linux-kbuild@vger.kernel.org>
References: <20080212174824.GA1919@kroah.com> <20080212.164149.209357519.davem@davemloft.net> <20080213084541.GA8091@uranus.ravnborg.org>
In-Reply-To: <20080213084541.GA8091@uranus.ravnborg.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200802140156.15325.zippel@linux-m68k.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1107
Lines: 41

Hi,

On Wednesday 13. February 2008, Sam Ravnborg wrote:

> config foo
> 	tristate "do you want foo?"
> 	depends on USB && BAR
> 	module
> 	  obj-$(CONFIG_FOO) += foo.o
> 	  foo-y := file1.o file2.o
> 	help
> 	  foo will allow you to explode your PC

I'm more thinking about something like this:

module foo [FOO]
	tristate "do you want foo?"
	depends on USB && BAR
	source file1.c
	source file2.c if BAZ

Avoiding direct Makefile fragments would give us far more flexibility in the 
final Makefile output.

> And we could introduce support for
>
> source "drivers/net/Kconfig.*"
>
> But then we would have to make the kconfig step mandatory
> for each build as we would otherwise not know if there
> were added any Kconfig files.

That's a real problem and it would be a step back of what we have right now, 
so I'm not exactly comfortable with it.

bye, Roman
--
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/