[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44.0702180017170.1150-100000@localhost.localdomain>
Date: Sun, 18 Feb 2007 00:22:10 -0500 (EST)
From: Kai Germaschewski <kai.germaschewski@....edu>
To: Tilman Schmidt <tilman@...p.cc>
cc: Adrian Bunk <bunk@...sta.de>, Hansjoerg Lipp <hjlipp@....de>,
gigaset307x-common@...ts.sourceforge.net, kkeil@...e.de,
kai.germaschewski@....de, isdn4linux@...tserv.isdn4linux.de,
linux-kernel@...r.kernel.org
Subject: Re: Kbuild problem
On Sat, 17 Feb 2007, Tilman Schmidt wrote:
> Alright, then so be it. But that raises another question:
> asyncdata.o is only needed for M105 and M101, not for the base
> driver. How do I express in Kbuild that asyncdata.o is to be added
> to gigaset-y only if CONFIG_GIGASET_M105 and CONFIG_GIGASET_M101
> are not both 'n'?
The way this is typically done is via Kconfig. Add a config option
ASYNCDATA (actually something more descriptive/specific would be better),
add a "select ASYNCDATA" to the config options for m101 and m105, and then
you can use CONFIG_ASYNCDATA to decide whether to add asyncdata.o in the
Makefile.
--Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists