mgorny added inline comments.
================ Comment at: clang/docs/UsersManual.rst:915 +in the directory where Clang resides. If Clang is started via an executable +without target prefix, Clang will use ``default.cfg`` instead. ---------------- sepavloff wrote: > What about using default config based on driver mode (clang.cfg, gcc.cfg > etc)? It looks like a more flexible solution, - different driver modes may > need different default settings. Even if these setting are identical, the > default config files may be links to one, say `clang.cfg` or just include > that file with `@file`. It's actually described below — you can have `default-clang.cfg`, `default-clang++.cfg`, etc. Using this naming makes it possible to use the same logic for default as for prefixed execs. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D109621/new/ https://reviews.llvm.org/D109621 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
