On Sat, Nov 23, 2013 at 1:27 AM, Hans Wennborg <[email protected]> wrote:

> On Thu, Nov 21, 2013 at 10:53 PM, Manuel Klimek <[email protected]> wrote:
> > I personally actually think we should somehow bake clang-format into the
> > extension (if possible) and distribute it via the visual studio gallery.
>
> Sounds great. Do you want to take a stab at this? ;)
>
> In any case, I won't worry about this for the 3.4 release. I feel bad
> trying to scramble to do this stuff way after the branch point.
>

Oh, this is totally not important for the 3.4 release - I just thought that
the multi-VS-version support is cool enough that it'd be good to have a
release of it on builds/.


>  - Hans
>
> > On Fri, Nov 22, 2013 at 7:05 AM, Kim Gräsman <[email protected]>
> wrote:
> >>
> >> On Fri, Nov 22, 2013 at 3:20 AM, Hans Wennborg <[email protected]>
> wrote:
> >> >> 2) The target audiences are fairly distinct. Most clang-format Visual
> >> >> Studio
> >> >> extension users likely don't want or need an LLVM installation. This
> is
> >> >> the
> >> >> crowd who'd benefit most from a single click installation on the
> >> >> download
> >> >> page that works the same way as other VS extensions.
> >> >>
> >> >> Wouldn't it make more sense to offer the Visual Studio extension as a
> >> >> separate download?
> >> >
> >> > If we want to support that, we should bake clang-format into the
> >> > extension itself.
> >> >
> >> > Manuel: maybe that's what we should be doing?
> >>
> >> I think that would make more sense. I'm already distributing private
> >> builds of clang-format to co-workers who've installed the extension,
> >> because the only way to get clang-format is to install all of LLVM.
> >>
> >> FWIW,
> >> - Kim
> >> _______________________________________________
> >> cfe-commits mailing list
> >> [email protected]
> >> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
> >
> >
>
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

Reply via email to