[Development] Change ANGLE 3rd party source from Google to Microsoft
Oliver Wolff
Oliver.Wolff at qt.io
Mon Aug 6 07:07:55 CEST 2018
Hi Brett,
On 03/08/2018 14:46, Stottlemyer, Brett (B.S.) wrote:
> On 8/3/18, 5:06 AM, "Development on behalf of Oliver Wolff" <development-bounces+bstottle=ford.com at qt-project.org on behalf of Oliver.Wolff at qt.io> wrote:
>
> Hi,
>
> Is everyone ok with this change? The ANGLE update from Google (which
> uses a revision that still supports MSVC 2015) would be ready
> (https://codereview.qt-project.org/#/c/233385/), but we would like to
> use a newer version from Microsoft for 5.12 if we can agree on this change.
>
> Just a quick look at the commit history shows Google’s version is under active development (last commit today) while Microsoft’s version is not (last commit, as of just now, was Oct 9th, 2017). So, the choice is using an old sha on a maintained repo, or HEAD of an unmaintained one? Hopefully that isn’t the case.
you seem to be correct. I will try to get in touch with them and ask
about the status.
>
> IIUC, Chromium moved to clang-cl builds for windows (see http://blog.llvm.org/2018/03/clang-is-now-used-to-build-chrome-for.html). What/how is QtWebEngine building for 64+ (chromium) on windows?
I think QtWebEngine does not use the ANGLE version shipped with qtbase,
but has another version of ANGLE shipped, but I will let someone from
the WebEngine team comment on that. For qtbase we need to build ANGLE
with MSVC 2015 and 2017 and with MinGW. Changing to clang-cl is not an
option there.
>
> Thanks,
> Brett
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
More information about the Development
mailing list