On Sun, 28 Oct 2001 20:39:42 -0600,
Peter Samuelson <[EMAIL PROTECTED]> wrote:
>
> [peter]
>> >select_cond(CONFIG_ISDN slhc.o CONFIG_ISDN_PPP)
>
>[kaos]
>> That is worse, you can select a list of objects, where does the
>> second config go?
>
>You can also have a list of CONFIGs, can you not? In which case you
>have a parsing problem either way.
select() takes exactly one CONFIG_, select_cond() takes exactly two.
No kbuild 2.5 command takes a variable sized list of CONFIGs.
>I still don't see why the code can't just do as dep_tristate does: "if
>there exists an 'n', return 'n', else if there exists an 'm', return
>'m', else return 'y'".
# only included if CONFIG_ISDN != n
bool ' Support synchronous PPP' CONFIG_ISDN_PPP
CONFIG_ISDN controls if the overall isdn code is built and how it is
built. CONFIG_ISDN_PPP selects slhc.o using a boolean statement but
the result is really tristate.
CONFIG_ISDN CONFIG_ISDN_PPP slhc.o
n - n
y n n
y y y
m n n
m y m
The first config has priority, the second only selects a subset. The
dep_tristate rules do not work for this case, we have quite a few in
the kernel.
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
