Having a separate 3rdparty_upstream might not be the best solution
after all, but oh well.

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

The new 3rdparty submodule contains snapshots of both ninja
and chromium. This drastically reduces the size of the repository
and can be used by our CI system.

Change-Id: Ie7482181f2ba9dba5fc181b1f221a5fae714c8c8
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

WebTouchEvents have a slightly different behavior than QTouchEvent in
that the type of the event is TouchStart for each new point press,
while Qt sends a TouchBegin only for the first point press.

Since we already need to use ui::TouchEvent to be able to use
ui::GestureRecognizer, always do this conversion first to also let
UpdateWebTouchEventAfterDispatch chose the proper event type.
Some of the code from render_widget_host_view_aura.cc was copied into
render_widget_host_view_qt.cpp to fill the needed functionality.

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

Add proper support for GYPINCLUDES in gyp_generation.
Rename the exclusion gypi to a more generic name so we
can use it for more intrusive changes (we'll need it for mac).

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

Change-Id: Ic261e5aa38b04632c019d577117e9fb205462d82
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

Adding several patches to the repository that need
to be applied to the chromium sources in order to allow
building on Mac.

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

Chromium is not using a regular git submodule based
repository layout. Therefore some special tweaking is
necessary.
This script will take care of setting the correct
submodule paths and references after cloning the
qtwebengine repository.
Further it also downloads and builds the ninja build tool.

Change-Id: I999ef33cbdbe3bfaff88253bb543ba77f5b68fd7
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Ideally we should find a way to use the binaries available
in src/third_parth/gold.

process uses the same code as lib and decides at runtime which
code to run. Fix the debug build by making sure that all infrastructure
code is available in both process and lib by building common code
not shared directly through chromium sources in a separate static lib.

Use a gypi files for that with target defaults with our file
exclusion patterns.
Another patch bites the dust !

This reverts commit 0e7244d61e01ab4f2e3532d274115903eae7a3d7
with a few improvements.
We now need to patch the shipped version of gyp in tools/gyp.

Changing the toplevel-dir does not work with libvpx's
evil gyp files. The unpack_lib_posix.sh script fails.
Therefore we cant use it for now.

We simply needed to specify the --toplevel-dir command line argument
when invoking gyp in order to get a sane out directory structure again.
Also update the README to reflect a bit better the current state of things.

This should allow us to have much better integration by generating the necessary gyp
files directly from qmake.
Mostly works for now, though we will most likely need to build the gyp generation
as we go.

  * Out dir logic is still crap and needs to be (re)worked.
  * In the same vein, we probably don't want the generated gyp
  content ending up in the source tree in the long run, which could prove tricky
  with relative paths to sources and all.

So we don't have to ensure GYP_GENERATORS is set properly.

We'll probably add a qmake wrapper for it later, but for now that should do.