On Sun, 28 Oct 2001 20:11:21 -0600, Peter Samuelson <[EMAIL PROTECTED]> wrote: >[kaos] >> select_cond(CONFIG_ISDN CONFIG_ISDN_PPP slhc.o) >> >> Both configs must be selected, either as 'y' or 'm'. The first config >> defined how the object is compiled. I am worried that this might be >> confusing, some users are bound to get the config options in the wrong >> order. Any ideas for a less ambiguous construct? > >select_cond(CONFIG_ISDN slhc.o CONFIG_ISDN_PPP)
That is worse, you can select a list of objects, where does the second config go? >Come to think of it, does it really matter what order the CONFIG >options come in? Isn't this more or less just like dep_tristate, which >does a boolean AND of the existing options anyway (say m==1, y==3)? No, the first config is the main one, the second config selects a subset of the main code. CONFIG_FOO=m CONFIG_BAR=y select_cond(CONFIG_FOO CONFIG_BAR object list) is different from select_cond(CONFIG_BAR CONFIG_FOO object list). The first builds the object list as modules, the second as built in. _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
