The script for aggregating the generated bindings suffered from
the same error on Windows as the other generator python scripts.

This should be fixed up when taking the next snapshot with the
commit 8f5515e8

.

Change-Id: Icd08dfa4bb09da806e9946b10af9984011dde463
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I172b552f0df8923d795a3c6f84c4fb4e1e780788
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Running python down into the WebKit directory structure and referring
a file relatively to the build directory can easily spill over the
260 char limit on Windows.

Resolve the absolute path using join and normpath to work around the
issue.

Change-Id: I6e89aad542761adcbd821b05f0cc6e9d489dced5
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This patch has been cherry-picked from upstream chromium,
as the GUARDED_BY annotation broke Qt builds on OSX with
older Xcode / clang versions.
Review URL: https://webrtc-codereview.appspot.com/14769004



Change-Id: Ib77d997f0c628e3bb378a06c427fbe938cd7dbc0
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Qt currently only use LF in its sources like git normally recommends
and QtWebEngine should do the same to avoid edge cases in the
packaging process.

take_snapshot will normally take care of this for future branches.

Change-Id: I47c4ef2db89361819ded864e3ba95e161ad10a92
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

The previous logic led to problems when running 64 bit
builds in a native 64 bit shell as the cross compiler
was always given priority.

Change-Id: Id6a29147c461e8542f65a568ff5956d4fdb3c642
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

Chromium is always producing and consuming the textures on the GPU
thread, switching the GL context accordingly, and are using sync
points to externally know when it is correct to send the consumming
GL commands down the pipe of their respective GL context.

Since Qt is consuming those textures in a different thread,
synchronizing when commands are handed down to GL isn't always enough.
The GL driver could decide to do additional scheduling and end up
executing Qt's consuming GL commands before Chromium's producing ones
even if they were sent to their respective context in the right order.

To prevent this, convert each sync point into a real GL fence sync
and allow Qt to communicate the dependency between consuming and
producing commands down to GL even across threads.

gfx::GLFence can now be converted to a POD TransferableFence to allow
waiting for or destroying the sync using a QOpenGLContext, which
gl_fence.cc wouldn't be able to use through Chromium's GL function
table.

Change-Id: I8a9e2de6ed84b2e16f5504c5d66dc3580b87140a
Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Reviewed-by: Michael Bruning <michael.bruning@digia.com>

This patch can be removed again as soon as
we do not need to support XCode <= 5.0 anymore.

Change-Id: Icdcca203f28555029a16ce7f8a806f2844ecb0b4
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

This patch applies the Qt scroll animation configuration from WebKit.
This makes the scrolling more responsive and smooth when used with
touchpad scroll gestures or free spinning scroll wheels.

Change-Id: I2f17185f3e95c6bc84608cc4c3945dba2d67faa8
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Adding the -S argument to skip import site seems to be causing some
issues on our CI for now.

Change-Id: I551c85b580ce1e148517202c884ae95df5adc841
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

Skia freetype will enforce slight hinting in SkTypeface_FreeType::onFilterRec
when subpixel positioning is enabled. To avoid overriding medium hinting
with slight, we should not enable subpixel positioning for medium hinting
similar to how it is avoided for full hinting as well.

Change-Id: I4a229cf2b8827c11f33789d1c35c2d0eaeaed0ae
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Just having the conditions match triggers pkg-config to be run
which will fail the build even if we won't need the library.

Change-Id: Ic8556f3019ff6c5e76d609e9f67d68ec2a9a392e
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Including the gyp files forces the resources to be available in the
snapshot to allow grit to succeed.

Add a wrapping condition that explicitly includes supported
components in Qt builds.

Change-Id: I17d477f2bc26b35a0031830af087c81854951389
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This also removes the cacheinvalidation directory that is excluded
in the last version of take_snapshot.py.

Change-Id: I4ebdbe108c13bdd76b977d1e8d24f54ca6796f01
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

ATL currently isn't distributed with MSVS Express, only with the
Professional version. Chromium requires downloading the WDK iso for
express users just to be able to use the ATL version that was shipped
with it.

We can avoid the extra dependency for now by cutting off all the
accessibility code, which is currently the only part of the content
layer depending on ATL. We will use the Qt accessibility code anyway.

Change-Id: Iec25231250ccfc9405fdf342752733814888f348
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

We want to use this option to prevent gyp from detecting the MSVC
toolchain by itself. We already require the environment to be setup
according to the desired toolchain for Qt, and we should respect it
when it's time to build QtWebEngine through gyp.

win_tool.py currently expects the environment.<arch> file to be
present. Fix the issue by copying in this file the whole environment
at the gyp invocation time instead of from an invocation of the
setup script when ninja_use_custom_environment_files isn't used.

Change-Id: Iade4c488e1af5cab8306e9070c73d42ec67a955a
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Since we have little chance of introducing warnings in Chromium code
and that we allow building the code on more various toolchains,
avoid breaking the build for warnings.

We already disable them on os_posix==1 and OS!="mac" by overriding
the werror% gyp variable in qtwebengine_extras.gypi.

Change-Id: Ic233bcd018a9a78a508772dea126435e2226b721
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Qt will always use QLibraryInfo to determine where this file was
installed, regardless of the platform.

Change-Id: I79374655356d872b2bc766ec8a33fcba343e9c95
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

We do not support loading the chrome://tracing

 WebUI and therefore
we shouldn't bundle those resources in our library.

Change-Id: If3aa4c676b22a55e772f19487e21b4cd48babe65
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

We do not need courgette and have it excluded from our snapshot.

The original change doesn't explain why the dependency was added:
https://codereview.chromium.org/25909005/



Change-Id: I7d2c76343d1d223c2135e0b93facc279e74ff91c
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This is needed by the implementation of loadVisuallyCommitted in the QtWebEngine.

Change-Id: Ic0fcdc00f7963ea1088a1ae910bb2dbe26e9e12c
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Essentially cutting away the unnecessary part that depends on
extensions.

Change-Id: I8adbc77dca393ab8480e9cdea3c5c953b52c8aef
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

WebGL crashes when chromium is compiled with gcc 4.9,
because TSymbolTableLevel::~TSymbolTableLevel does
double delete of e.g. TFunctions because they are
inserted in the table with both their name and
mangled name.

The fix for this should reach stable with m37.
https://code.google.com/p/angleproject/issues/detail?id=651

Patch by Mike Hommey <mh+mozilla@glandium.org>
https://bugzilla.mozilla.org/show_bug.cgi?id=1025576



Change-Id: I0571478759666bcb55633dd4e630c5b42216d949
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This is part of using the ANGLE that is built / installed by Qt.

Change-Id: Ib71d47392690dab6cf874aec13db9e98710de684
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This moves libEGL and libGLESv2 from dependencies to
libraries where needed.

This also adds support for using the correct configuration
of the ANGLE libraries for linking and runtime loading.

Change-Id: I8c3a5eb11517bf03e921b257eeb3a34b7bc841ea
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This fixes the ASSERT that was triggerd on Windows in
PlatformKeyboardEvent::disambiguateKeyDownEvent  because
we do our own conversion from native events to web events.

This is the same way it was handled in the Qt specific
PlatformKeyboardEvent in WebKit.

Change-Id: I177c238bde1e0101b6abe9d5bbe3ba2e47908f1a
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

The linux kernel now reports the processor information
in "model name" and not in "Processor" anymore.
Both should be checked for backwards compatibility.

As described by:
https://code.google.com/p/v8/issues/detail?id=3112#c16



Change-Id: I567a72c18f43a483e7576e880c2d383873f5660f
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Since we're never going to statically link to the runtime library on
Windows (unlink Chromium when built as a monolitic chrome.exe), make
sure that our /M flag setting is also properly set for V8.

Change-Id: I755c3c0bfa27e45b897a2d4d5496103913d1c6c4
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

When replacing substrings with values from a dictionary,
the replacements should not be truncated to the length of src_root_dir.

If the basename does not exist as a key in the resource_ids file,
then fall back to an absolute path.

The precedence is like:
file in chromium > file basename > absolute file name.

THIS SHOULD BE UPSTREAMABLE.

Change-Id: I7d1da8c04515807000742aac4a6fa4db7616fd13
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This adds a let_qmake_do_the_linking target variable to tell ninja
not to link but rather dump the linking information from gyp in a
file that we'll parse with qmake.

Change-Id: I753888776679e449d7a64b6bf5b47e7a60dfa827
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: Ifbe063950d14d8388e3c8c1d6cebdfae5cbdb8ae
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I3fcbf166978cf20f7a07d7e6bda135864054e9c1
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

We require that the icu libs are in the default library seach path.

Change-Id: Ia4981781f4239617831909da1250a61191a8c7dd
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

But fall back to chacha_vec_arm.S when arm_neon_optional
is used.

Change-Id: I1ea1f03d687c4b39fe4a322abb8ddb91113a1828
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I1bcc9cbb77b10e9e60d60900b9cfd8ce283947b0
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This is needed since https://codereview.chromium.org/106503003


and because of our chromium patch that fixes the build with a
GL ES2 configured Qt.

Change-Id: I2dfa1afe1bb58227656fee798a5d2549f88c3f9d
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I9997c3dead0f7d37c2a3c45082d5114d0f1632cf
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: I4a494bcda0e963430ab997664728d2a96f72188f
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

These threads are using the UI message loop on Windows per default. This
won't work since the UI message loop is handled by Qt and the Renderer
and GPU threads won't work with it properly.
Force these threads for using the default message loop as they use it on
Linux platform.

Change-Id: I8b04ba9070912378cf1d13173ddff48e98f9a49b
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

- Add Raspberry PI chipset to list of defined platforms.
- Make sure to include sources for xdg support.
- Do not use pkg-config-wrapper, as our sysroot pkg-config
  already returns absolute paths.
- Use openssl for eLinux.
- Use fontconfig and freetype2 for eLinux.

Change-Id: Ic5266f818432b4432ed1d8a1ac07f434cb5b86e6
Reviewed-by: Andras Becsi <andras.becsi@digia.com>