[Development] Moc with clang.

[Laszlo Papp]

It is really strange then they do not provide "mature" installers for the
mature parts.


On Wed, Jul 3, 2013 at 11:12 AM, Tr3wory <tr3w at freemail.hu> wrote:

> Maturity of clang on windows is a little complicated:
> First you can use 2 ABI: gcc/mingw or msvc.
> As far as I know the first is kind of working while the second has
> serious issues.
>
> Also the libc++ std library implementation has issues on windows,
> while the libstdc++ (from mingw 4.8) works.
>
> But this is about the clang used as a full compiler.
>
> If you use only the libclang as a c++ parser, then it's as good as
> everywhere else. And the moc-ng used as a drop in replacement of moc
> use only this. (Using as a clang plugin is a different story.)
>
> tr3w
>
> On Tue, Jul 2, 2013 at 6:05 PM, Laszlo Papp <lpapp at kde.org> wrote:
> > On Tue, Jul 2, 2013 at 3:24 PM, Konstantin Tokarev <annulen at yandex.ru>
> > wrote:
> >>
> >> > So, it could not be even optional because clang is not mature enough
> on
> >> > Windows, and in other scenarios or there is any other reason?
> >>
> >> Clang is quite mature on Windows, at least when used as C++ parser.
> >
> >
> > Why I thought that was because I do not see pre-built Windows clang
> binaries
> > for the latest version, and even before that, it had been marked as
> > "Experimental". Not sure about 64 bit, debug, openmp (few projects still
> use
> > that, yeah), other scenarios, et cetera.
> >
> > Perhaps, if you build it yourself, it might work, but still. :-)
> >
> > Cheers,
> > Laszlo
> >
> > _______________________________________________
> > Development mailing list
> > Development at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> >
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130703/dae468c0/attachment.html>