Hi!
> > Does this fit what you had in mind?
>
> Yes it does.
>
> Now I'll ask if you think embedding this information in one of the C
> files for a module would be even nicer?
I kind of like to be able to grep over just Kconfig files, to find out
what is going on...
--
(english) http://www.liv
On Thu, Feb 14, 2008 at 01:56:13AM +0100, Roman Zippel wrote:
> 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
> >
On Thu, 14 Feb 2008, Roman Zippel wrote:
> 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 allo
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 thin
Sam Ravnborg wrote:
On Wed, Feb 13, 2008 at 12:54:33AM -0800, David Miller wrote:
From: Sam Ravnborg <[EMAIL PROTECTED]>
Date: Wed, 13 Feb 2008 09:45:41 +0100
So we could do:
config foo
tristate "do you want foo?"
depends on USB && BAR
module
obj-$(CONFIG_FOO
From: Sam Ravnborg <[EMAIL PROTECTED]>
Date: Wed, 13 Feb 2008 10:04:51 +0100
> On Wed, Feb 13, 2008 at 12:54:33AM -0800, David Miller wrote:
> > Also, we need to make sure we can properly handle top-level
> > container-like items. For example, where would menuconfigs like
> > NETDEV_1 go if w
On Wed, Feb 13, 2008 at 12:54:33AM -0800, David Miller wrote:
> From: Sam Ravnborg <[EMAIL PROTECTED]>
> Date: Wed, 13 Feb 2008 09:45:41 +0100
>
> > So we could do:
> >
> > config foo
> > tristate "do you want foo?"
> > depends on USB && BAR
> > module
> > obj-$(CONFIG_FOO) += f
From: Sam Ravnborg <[EMAIL PROTECTED]>
Date: Wed, 13 Feb 2008 09:45:41 +0100
> So we could do:
>
> 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 al
>
> 2) Let's move away from some/dir/{Kconfig,Makefile} schemes and
>instead have each "thing" have it's own Kconfig.foo or
>Makefile.foo that gets automatically sucked into the main
>directory Makefile or Kconfig using file globs or similar.
So we could do:
config foo
trista
9 matches
Mail list logo