[cfe-dev] VS2017: LLVM Compiler Toolchain Plugin
Zachary Turner via cfe-dev
cfe-dev at lists.llvm.org
Mon Oct 1 10:29:57 PDT 2018
It occurred to me there is one case where I think showing filenames is not
only helpful, but necessary. It is the case where you specify multiple
file names on a single command line invocation.
Most build systems will not ever invoke this, but the compiler does, and
without printing filenames to stdout it will be impossible for the user to
know what's happening in this case.
On Mon, Oct 1, 2018 at 5:52 AM Hans Wennborg via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> On Sat, Sep 29, 2018 at 8:06 PM, Stephen Kelly via cfe-dev
> <cfe-dev at lists.llvm.org> wrote:
> > On 29/09/18 15:54, Zachary Turner via cfe-dev wrote:
> >> To be clear, there’s no disagreement that when using MSBuild you should
> >> have exactly the same experience with clang-cl and cl. And by exact same
> >> experience, that means if anything is going on behind the scenes to make
> >> sure the filename is printed, it should be invisible to the user.
> > Hmm, I don't know what MSBuild has to do with it. Why shouldn't the
> > experience be the same with Ninja, or another buildsystem, or just when
> > running both from the command line? Maybe this is where I'm missing
> > something.
> It's not a goal of clang-cl to emulate MSVC perfectly. It's just
> aiming to be compatible so that's it's easy for users to switch
> between them. The goal is to be better than MSVC :-)
> I think the behaviour of not echoing the filename is better and should
> be the default, but I can see that it's useful when using a build
> system that doesn't provide any separate indication of progress, so
> let's add a /showFilenames flag as discussed on
> I will try to get a patch out unless someone beats me to it.
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev