[lkml]   [2008]   [Feb]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: distributed module configuration [Was: Announce: Linux-next (Or Andrew's dream :-))]

    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

     \ /
      Last update: 2008-02-14 02:01    [W:0.020 / U:0.900 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site