[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. Distinguishing between a CONFIG option and an object file may not make for a pretty parser, but it is not difficult. Any hacker who names a file CONFIG_FOO.c deserves what he gets. > >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. 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'". Is there a functional reason not to do this, or is it merely a matter of awkwardness in the generated makefile? Peter _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
