summaryrefslogtreecommitdiffstats
path: root/patches
Commit message (Collapse)AuthorAgeFilesLines
* Update init-repository.py to allow using upstream chromium repository.Zeno Albisser2013-08-191-1/+1
| | | | | | | | | | | | | | | | | | | | The regular workflow now is just to clone the qtwebengine repository and then execute the following commands. git submodule init && git submodule update --recursive && qmake && make This will also clone a submodule called 3rdparty which contains the chromium and ninja sources without pulling in further submodules and without a complete history. Developers that do want to have a complete chromium checkout instead should not use the above command sequence. Instead they should just clone qtwebengine, execute the init-repository.py script, run qmake and make. The init-repository.py script will then checkout the complete chromium sources into a subdirectory called 3rdparty_upstream. The location of these sources will be picked up by qmake automatically. Change-Id: I0fa4f1d554bdca2e852b6a97aa2e5462d90d8664 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Add patch for WebKit after updating Chromium.Zeno Albisser2013-08-172-0/+69
| | | | | | | | | | | | | Including Assertions.h leads to __darwin_ssize_t being defined inside namespace WebKit but not outside that namespace. This is because certain headers will not be pulled in again later on in the same compilation unit. This patch has already been upstreamed, and can be removed with the next Chromium update. Change-Id: I302bbf779fcabb909a9ffda53d8b9fdccc87e248 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Update patch for touch and gestures after updating Chromium.Zeno Albisser2013-08-171-10/+10
| | | | | Change-Id: I64aa8e01e3d157670f2fd118d1ed25730b61a967 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Update Clang libcc patch after updating Chromium.Zeno Albisser2013-08-171-39/+38
| | | | | | | | - googleurl headers are now in url/. - dom_storage_namespace.h moved. Change-Id: I87f08d2426ac0da5b50fcf424ca446fb03f207fd Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Update patch for using libc++ instead of stdlibc++ after updating chromium.Zeno Albisser2013-08-171-12/+12
| | | | | Change-Id: I93ceb4e5d1ccf63cbeaec1fdff4ab1c5c8a57a65 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Add patch for newer XCode/clang versions on Mac.Zeno Albisser2013-08-082-0/+39
| | | | | | | | | | | Remove -Wno-deprecated-register from common.gypi. This warning is not supported by recent clang versions shipping with XCode. Therefore replacing it with -Wno-deprecated. This is a bit a too broad fix, but the best we can do for now. It seems that the flag is still supported in upstream clang. Change-Id: I609355484c9b3ae111591a17181f02104bed6b6b Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Remove hunks that accidentially ended up in Clang-libcpp patch.Zeno Albisser2013-08-081-39/+0
| | | | | Change-Id: Ib592d8498cabdafda0dc65cf81de4721f139ffc8 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Transform QTouchEvent into ui::TouchEvent first.Jocelyn Turcotte2013-08-012-0/+68
| | | | | | | | | | | | | | | 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>
* Make init-repository.py properly reset all submodules.Zeno Albisser2013-07-281-4/+0
| | | | | | | | | | | | | With this patch init-repository.py will also abort uncommited git am/merge/rebase sessions and it will do a git reset --hard on every submodule. We are no longer executing a 'git submodule update --recursive' in the patch-chromium.sh script, since init-repository.py takes care of checking out the proper revisions. Change-Id: I6cc50944d888ffce5e3d282500dffe3daffecdf4 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Add patch for grit after updating Chromium.Zeno Albisser2013-07-242-0/+50
| | | | | Change-Id: I9e197aafd3dd342ba965ac27ae3b2543cd377bf3 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Update patches after updating Chromium.Zeno Albisser2013-07-243-42/+114
| | | | | Change-Id: I6d0cf5ada32594d91c680518868055fc03466ac7 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Get rid of or upstream chrome_path patch for zygoteAndras Becsi2013-07-092-16/+2
| | | | | | | | | | | | | Override base::FILE_EXE in ContentMainDelegateQt::PreSandboxStartup() with the path to our child process and get rid of the command line argument and the content::CHILD_PROCESS_EXE override. This reduces 0001-My-local-fixes.patch to export ContentMainRunner so the patch can be renamed to better reflect it's purpose. This hunk is still needed since we need to access ContentMainRunner's Initialize() to set our ContentMainDelegate. Change-Id: I808cb114100300a33f8cb1b154c6cde89cbf5d98 Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
* Get rid of the need to export content::GetContentClient()Andras Becsi2013-07-091-13/+0
| | | | | | | | | | | ContentBrowserClientQt is a singleton which makes it possible to access it from WebContentsViewQt and removes the need for patching chromium. This is similar to how ShellContentBrowserClient is managed in the content shell. Change-Id: I67f35520935388888c7230806ad543a58b3211c3 Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
* Do not warn for header-hygiene.Zeno Albisser2013-07-032-0/+30
| | | | | | | | | | | QtDeclarative is consciously leaking the namespace QtQml. Therefore clang would warn about header hygiene. Unfortunately this cannot be fixed in QtDeclarative, unless we accept not to be able to use QtQuick1 and QtQuick2 in the same application. Change-Id: I5ba78eb20f98e2e04d9c190794c83710b7f196e4 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* [Mac] Do not modify the child path.Zeno Albisser2013-07-022-0/+30
| | | | | | | | | | We currently only have a single process binary for Qt. Therefore we should not choose a different binary based on required privileges. However, this patch can only be a preliminary solution. May be we should instead implement our own ChildProcessHost. Change-Id: I0e76ff44f474842c7a96317a05f9964782f68080 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Add Mac support.Zeno Albisser2013-06-275-2/+1109
| | | | | | | | | 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>
* Remove gclient commands from patch_chromium script.Zeno Albisser2013-06-271-21/+12
| | | | | | | | | | | The new submodule layout does not need gclient anymore. Instead it relies on the init-repository.py script and git submodule. We are still checking for CHROMIUM_SRC_DIR for the time being. Just in case somebody still wants to use external chromium sources. In this case it will be necessary to master gclient manually though. Change-Id: I1633cda873c94fd86433be1f60fd422c7f230cb2 Reviewed-by: Andras Becsi <andras.becsi@digia.com>
* Adding some missing license headersSergio Ahumada2013-06-251-0/+41
| | | | | Change-Id: If41e2991be7877060f7739877f756acf2679b688 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* better gclient detection in the patch scriptPierre Rossi2013-06-191-4/+13
|
* Allow running patch-chromium.sh from any directory.Zeno Albisser2013-06-191-1/+1
|
* Get rid of BlinqApplication.Jocelyn Turcotte2013-06-113-7/+40
| | | | | | | | Rename the class to WebEngineContext and keep it as a ref-counted member of pages instead. Also: - Change the user-agent product to QtWebEngine - Don't pass actual command line arguments to Chromium anymore - Allow attaching to the event loop through Before/AfterRun instead of blocking
* Allow excluding source files from the chromium buildPierre Rossi2013-06-032-39/+0
| | | | | | Use a gypi files for that with target defaults with our file exclusion patterns. Another patch bites the dust !
* Remove Qt specific m_window member from Shell.Zeno Albisser2013-05-314-177/+39
| | | | Unfortunately this requires some minor reinterpret_casts.
* do not update chromium by default.Zeno Albisser2013-05-311-2/+6
|
* Make use of OverrideCreateWebContentsView.Zeno Albisser2013-05-311-9/+0
|
* Add fetch step to the update script.Zeno Albisser2013-05-311-0/+1
|
* make the backingstore use a QPixmap instead of QBackingStoreZeno Albisser2013-05-311-7/+7
|
* add patch to remove render_widget_host_view_gtk / web_contents_gtk from build.Zeno Albisser2013-05-312-0/+35
|
* fix for bash.Zeno Albisser2013-05-151-1/+1
|
* Add an "update'n patch" scriptPierre Rossi2013-05-151-0/+24
| | | | And fix the shell_main_delegate include after things moved in chromium.
* Adding a preliminary implementation of shell_qt.Zeno Albisser2013-05-141-0/+150
|
* Re-introduce use of the dop level dirPierre Rossi2013-05-131-0/+32
| | | | | | This reverts commit 0e7244d61e01ab4f2e3532d274115903eae7a3d7 with a few improvements. We now need to patch the shipped version of gyp in tools/gyp.
* Messing around some moreSimon Hausmann2013-04-291-0/+60
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-10 22:03:52 +0000