Someone should tell Google who have recently ported it to Android.
On Wed, Jul 3, 2013 at 4:46 PM, Thiago Macieira
wrote:
> On quarta-feira, 3 de julho de 2013 13.12.02, Tr3wory wrote:
> > Also the libc++ std library implementation has issues on windows,
>
> libc++ isn't meant to work outside of
On quarta-feira, 3 de julho de 2013 13.12.02, Tr3wory wrote:
> Also the libc++ std library implementation has issues on windows,
libc++ isn't meant to work outside of OS X.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.
If a project releases binary packages for a given OS, but they aren't able
to make binaries for the latest version and if the latest release for that
OS is marked experimental, then that fits my definition of "not mature".
Also, not having 64bit doesn't point to much maturity (nor does forcing
fix
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 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
On Tue, Jul 2, 2013 at 3:24 PM, Konstantin Tokarev 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 be
On Tue, Jul 2, 2013 at 10:51 AM, Olivier Goffart wrote:
> Hi,
>
> For those who do not read planetqt.org, I would like to mention here that
> I
> have experimented to re-implement the moc (MetaObject Compiler) using
> liblang
> as a parser.
>
> The blog post say it all: http://woboq.com/blog/moc
