On Thu, Nov 29, 2001 at 01:30:27PM -0500, Eric S. Raymond wrote: > Tom Rini <[EMAIL PROTECTED]>: > > I don't know. How is it harder to validate > > choice kernel_format_PPC > > VMLINUX ZIMAGE ZNETBOOT > > default ZIMAGE > > choice kernel_format_ix86 > > VMLINUX ZIMAGE BZIMAGE BZDISK > > default BZIMAGE > > Than: > > choice kernel_format > > VMLINUX ZIMAGE BZIMAGE ZNETBOOT > > defeult ((X86) : BZIMAGE ? ((IA64 or SPARC) ? VMLINUZ : ZIMAGE)) > > unless X86 suppress BZIMAGE > > unless PPC suppress ZNETBOOT > > That's not a bad case. The case I'm worried about is the one where the > choice menus get split into different files and can't be eyeballed at > the same time easily.
Me too. I'm sort of lost as to why this would all need to be in one file. If I understand things, there's one rules.cml for compile target and 'install' questions. Why? There will be per-arch questions which have no relevance to other arches. But even if those were each in a different rules.cml, I still don't see the problem. If there's a syntax error, the compiler will throw up and tell us where, right? What's a bad thing that could happen? > > > There's a problem like this now with unless/suppress declarations, but > > > I saw no way to avoid it there. > > > > I guess I didn't read the other posts thourghly enough, what's the exact > > problem? > > Information distributed through the ruleset in such a way that it's hard > to know all the places a given symbol participates. On the compiler side of things or the human side of things? All of the rule files become one big file, sort of anyhow don't they? And if someone is asking about FOO in a horribly wierd (file) place, maybe they have a good reason to.. Or are totally missing something and will end up with some wierd behavior possibly. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
