2 ms·
Not for <version>, or just for <version>. Rather, for being able to designate header names without worry about what files have been shoveled into random directo
by ncmncm 7y ago
Not for <version>, or just for <version>. Rather, for being able to designate header names without worry about what files have been shoveled into random directories.
It really is on the compiler implementers for not providing a better accommodation to this very predictable problem.
That said, fixing the autoconf scripts may be the most immediate route to sanity for the "config.h" / <version> case, eliminating the problem at its source.
- a1369209993 7y ago> for being able to designate header names In other words, there's no reason why '#include <foo>' should ever be looking in the translation unit's directory; that's what '#include "foo"' is for.
- ncmncm 7y agoI bet autoconf actually says "-I $top_level" or some such. What's mad is that -I controls where <> names are searched.
- kazinator 7y agoI concur. -I is a traditional option from Unix compilers with a very silly behavior; but for years now we have had something called -iquote in gcc (and clang). Before -iquote, there was -I- which is deprecated.