[cfe-dev] VS2017: LLVM Compiler Toolchain Plugin

[Zachary Turner via cfe-dev]

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.

The question is about what to do when not using MSBuild. Someone on Linux
who is running clang-cl from the command line would be disturbed by the
output because it’s not standard behavior for tools on Linux to do that.

With the implementation strategy I proposed in the earlier message, it
seems like we can have the best of both worlds. There’s only really one
tool I’m aware of that requires this output (MSBuild), and all other use
cases seem to prefer not having it.
On Sat, Sep 29, 2018 at 1:23 AM Stephen Kelly via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

> On 28/09/18 23:30, Zachary Turner via cfe-dev wrote:
> > I hadn’t seen that blog post, thanks!
> >
> > I don’t have a particularly strong opinion on the stdout option, but
> > several other project members do. Can you elaborate on why you think it
> > should be on by default
>
> Consistency with MSVC.
>
> I'll quote you on this:
>
>  > stdout.  Currently when you build a large project you see no output and
>  > it looks like the build is hung, potentially for several minutes.  It
>  > would be nice to match what msvc does and generate build output
>
> That's the exact experience I had.
>
> > (and separately, why it should not be possible
> > to disable)?
>
> Self consistency. This is less important I think.
>
> > The thinking on our side is that this is a task better
> > handled by the build system
>
> There are many more buildsystems than Clang-CLs.
>
> > , and presently most build systems today just
> > end up filtering this out anyway.
>
> I'm not aware of that.
>
> > My current idea for how to implement this is to have clang detect the
> > presence of a magical undocumented environment variable, and have the
> > MSBuild integration just set this variable.
>
> I don't understand the reasoning behind deliberately diverging from what
> MSVC does in a tool which emulates it.
>
> I can keep my patch around if I need to anyway. I just thought I'd point
> to to the bug report so you could see the existing discussion.
>
> Thanks,
>
> Stephen.
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20180929/addf3671/attachment.html>