summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix build with QtDeclarative 6.11Allan Sandfeld Jensen2025-06-181-1/+1
| | | | | | | | | getV4Engine() was removed, and never needed in Qt6. Pick-to: 6.10 Fixes: QTBUG-137854 Change-Id: I50f168bd7dae2523632705a0612450345dff5117 Reviewed-by: Ulf Hermann <[email protected]>
* Remove logging category macro version checksKaloyan Chehlarski2025-06-132-6/+2
| | | | | | | | | | | The version checks were already wrong, because we also need to support building 6.11 on top of 6.8, assuming 6.11 is the next LTS. Instead of fixing them, this commit removes them entirely, to avoid future submodule update breakage. The explanatory comments have been amended to correctly reflect when the workaround macros should actually be removed. Change-Id: Iff894be9697a63eec67ddbe815617b1069e74e3b Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Update ChromiumMichal Klocek2025-06-122-1/+1
| | | | | | | | | | | | | Submodule src/3rdparty cc9ba81d..d55e428c: * [Backport] Security bug 420637585 * [backport] CVE-2025-5068 (2/2) * [backport] CVE-2025-5068 (1/2) * [backport] CVE-2025-5419 Pick-to: 6.10 Fixes: QTBUG-137383 Change-Id: Iab29ac0cc8117b519485d2a9683ee0babc1d2d59 Reviewed-by: Anu Aliyas <[email protected]>
* Update ChromiumMichal Klocek2025-06-122-1/+1
| | | | | | | | | | | | | | | Submodule src/3rdparty 059a95d6..cc9ba81d: * [backport] Security bug 408294914 * [backport] Security bug 325123679 * [backport] Security bug 407898107 (3/3) * [backport] Security bug 407898107 (2/3) * [backport] Security bug 407898107 (1/3) * Add new functionalities to the Extension WebUI Pick-to: 6.10 Fixes: QTBUG-137362 Change-Id: I4194f1554a413be9409237c7619122eff07c402b Reviewed-by: Anu Aliyas <[email protected]>
* Update Extension WebUI page handler to support new functionalitiesAnu Aliyas2025-06-122-12/+114
| | | | | | | | | | | | Updated Extenion WebUI page handler to support thh efollowing functionalities. - Install extension - Unload and Uninstall extension - Disable extension Pick-to: 6.10 Change-Id: Ib47f2fe7cf562aa4c4148942e8f67e22d9c76455 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Support chrome.management APIMartin Negyokru2025-06-119-1/+226
| | | | | | | | | | Implement ManagementAPIDelegate. Add ManagementPolicy to the extension system. Pick-to: 6.10 Task-number: QTBUG-61676 Change-Id: If05aa7cb0ebfe860954e88eb794dd06aa6ae973a Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Docs: Qt WebEngine documentation doesn't mention the module requirementsAlexei Cazacov2025-06-061-1/+4
| | | | | | | | | This commit adds a note with optional dependences. Fixes: QTBUG-133608 Pick-to: 6.10 6.9 6.8 Change-Id: I9ac4971e2a8b0cbde754a249fb6115112a7fac96 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Doc: Add Security Considerations page to Qt WebEngineJerome Pasion2025-06-062-0/+69
| | | | | | | | | | | | We need to give security related information to application developers. For Qt WebEngine, a link to the Chromium and Qt security pages are good resources for developers. There is a mention of important web-related issues such as cross-site scripting and untrusted data. Task-number: QTBUG-133086 Pick-to: 6.9 6.10 Change-Id: I90cbcaa801790910aa9880060b4d0d7f9a999dad Reviewed-by: Moss Heim <[email protected]>
* Support chrome.system.storage APIMartin Negyokru2025-06-061-0/+2
| | | | | | | | | Initialize the StorageMonitor at startup. Pick-to: 6.10 Task-number: QTBUG-61676 Change-Id: Ic10bd1d012f80c3f231105ea15d466716311cd5c Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Support chrome.system.displayMartin Negyokru2025-06-065-0/+31
| | | | | | | | | | Add simple wrapper for DisplayInfoProvider to make it default constructable. Pick-to: 6.10 Task-number: QTBUG-61676 Change-Id: I3bcb37e7fc687e2226631d2b1a6875383e0bf469 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Fix accessibility for <p> tags with Windows NarratorKaloyan Chehlarski2025-06-051-1/+1
| | | | | | | | | | | | | | | | QAccessible::Paragraph maps to a Text control on Windows, which causes Narrator to completely ignore its child nodes. Since even a simple <p>Content</p> generates two nodes, a nameless parent kParagraph and a named child kStaticText, the result is that Narrator will see a Text node with no name, and simply read "text". This change maps the kParagraph role to QAccessible::Grouping, which allows Narrator to see its child nodes and read their contents aloud. Fixes: QTBUG-134055 Pick-to: 6.10 6.9 6.8 Change-Id: I96d4262bd4149f1dec50d47491263d0b022d4b83 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Fix accessibility for tablesKaloyan Chehlarski2025-06-052-41/+156
| | | | | | | | | | | | | | | | | | | | | | | | | | This change modifies a few of the table-related methods inside BrowserAccessibilityInterface to use corresponding specialty methods from Chromium's a11y implementation, instead of relying on manually extracted attributes. This fixes table contents always being reported as 'blank' to screen readers. The kRowHeader and kColumnHeader roles are now exposed as Cell to Qt (and thus, to the system), which is consistent with what Chromium does; exposing them to Qt as QAccessible::Row/ColumnHeader causes some issues when navigating with VoiceOver on macOS. The caption() method is now implemented as well. macOS-only implementations of certain platform methods related to tables have been copied over as well. This fixes some crashes when iterating through children. As a drive-by, this also fixes a rare a11y-related crash when in the middle of deleting a page. Pick-to: 6.10 6.9 6.8 Fixes: QTBUG-136622 Change-Id: I157bece10d3c2261722d7f70e2b879c1d462b137 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Fix QWebEngineLoadingInfo::errorString()Szabolcs David2025-06-053-6/+12
| | | | | | | | | | | | | | When we try to deduce error messages from HTTP error codes, the result of error_page::LocalizedError::GetErrorDetails() can contain empty HTML placeholders for the host name or the full URL. Replace these with proper URL information to get grammatically correct error description. Moreover, prevent filling errorString with misleading error message when the load was actually successful. Pick-to: 6.10 Change-Id: I6ef589e6d31336a4916eb28b17ca14fac56c61a1 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Doc: Enable automatic linking to sources on code.qt.ioTopi Reinio2025-06-052-0/+6
| | | | | | | | | | | | | Since 6.10, QDoc is capable of generating links to the declaration in the source code for each documented C++ API entity in their `Detailed description`. Add the required configuration to enable this feature for modules in qtwebengine. Pick-to: 6.10 Change-Id: Iab5a519f5d7bc15da0ca2d64dee374db72b245f1 Reviewed-by: Topi Reiniö <[email protected]>
* Make possible to use system EGL instead of ANGLE on LinuxPeter Varga2025-06-057-29/+119
| | | | | | | | | | | | | | | | | This is not the same direct EGL rendering solution what we used to have before QtWebEngine 6.9. With this configuration, the texture is accessed via NativePixmap instead of using shared GL context. Thus this implementation doesn't need adaptations in Chromium. This configuration is meant to be used for identifying ANGLE specific issues. Enable it with: --webEngineArgs --use-gl=egl Pick-to: 6.10 Change-Id: Ib8db5573b2001157eaee799c6b333f722ab87604 Reviewed-by: Moss Heim <[email protected]>
* Make possible to use fake GL API with VulkanPeter Varga2025-06-053-5/+10
| | | | | | | | | | | | | | | This configuration disables ANGLE but it still renders with Vulkan. Enable it with: --webEngineArgs --enable-features=Vulkan --use-vulkan=native --use-gl=stub WebGL is not expected to work with this configuration since it requires real GL API. Pick-to: 6.10 Change-Id: I7bc292e0c131c2cebe345f70bd3163dd3e6b2972 Reviewed-by: Moss Heim <[email protected]>
* NativeSkiaOutputDevice: Set color type according to NativePixmap supportPeter Varga2025-06-054-21/+46
| | | | | | | | | | NativePixmapEGLX11Binding requires the BGRA_8888 color type, use it for the check too. The GL graphics context doesn't necessarily mean that we need BGRA. Pick-to: 6.10 Change-Id: I41a4f1f6da94c10f8e6843e6edfed913bb98fabd Reviewed-by: Moss Heim <[email protected]>
* Clean up GL and Vulkan type detectionPeter Varga2025-06-041-83/+122
| | | | | | Pick-to: 6.10 Change-Id: I7add950538fb8782257de0eff45d8ee1b2010a9a Reviewed-by: Moss Heim <[email protected]>
* Remove --enable-webgl-software-renderingPeter Varga2025-06-042-19/+6
| | | | | | | | | | | | | | | Most probably it is useless with the new default ANGLE backend. The original code has been trimmed and now it is just equivalent with passing the following command line arguments: --webEngineArgs --disable-gpu-rasterization --ignore-gpu-blocklist As a drive-by, change WebEngineContext::initCommandLine() parameter to pointer instead of reference to make it clear on the caller side it will not use but it is expected to change the parameter's value. Pick-to: 6.10 Change-Id: Ic118fa55071c5d8ac0730db2f640c3132375db8b Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Add GBM information to context logPeter Varga2025-06-041-0/+1
| | | | | | Pick-to: 6.10 Change-Id: Ia2c07b887be65da0b45febc29c339e6a3b1e46bc Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Normalize signal/slot signatures 2025Marc Mutz2025-06-044-5/+5
| | | | | | | | | | | This is the result of running util/normalize on the code base. The following manual edits were needed: (none) Pick-to: 6.10 6.9 6.8 6.5 Change-Id: Ia59174aaf154559f7445e13d059723a282f75aae Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* cmake: PdfWidgets/Quick - fix dependenciesTim Blechmann2025-06-042-2/+9
| | | | | | | | | | | PdfWidgets and QdfQuick should publicly depend on Qt::Pdf/Quick and only privately on PdfPrivate / QuickPrivate Amends 209778ed9a167c156b448689191d2a6a381a6880 Fixes: QTBUG-135974 Pick-to: 6.9 6.10 Change-Id: I9cdcc6d6fd6cd0a11691025580f2fd4a41325282 Reviewed-by: Alexandru Croitor <[email protected]>
* Support chrome.runtime APIMartin Negyokru2025-06-049-3/+159
| | | | | | | | | Implement RuntimeAPIDelegate methods which are required by the runtime API. Pick-to: 6.10 Task-number: QTBUG-61676 Change-Id: Ic73f34bafc51abd69696a0affe5657f953391349 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Allow V8 script extensions in extension service workersMartin Negyokru2025-06-042-0/+7
| | | | | | | | | | Enable V8 builtin objects in service workers. Fixes '[FATAL:safe_builtins.cc(163)] Check failed: value->IsObject(). Array' Pick-to: 6.10 Task-number: QTBUG-61676 Change-Id: I141cc5d778afd9aec37c6e057f6f9e486844a6bb Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Support extension service workersMartin Negyokru2025-06-044-0/+69
| | | | | | | | | | | | | | | | | | | | | Extension service workers are core part of the ManfestV3, replacing background scripts from ManifestV2. Extension APIs (eg. chrome.tabs) are only available in these script contexts. This change implements the required methods to setup worker contexts. * Forward the service worker events from the renderer to the extension binding system. The binding system responsible for adding the `chrome` object and other API objects to the context. * Register the ServiceWorkerHost interface binder to enable ipc between the browser process and service workers. Pick-to: 6.10 Task-number: QTBUG-61676 Change-Id: I68c539f5ce28b7a7293c325705248bb9eb53ddc0 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Update ChromiumMichal Klocek2025-06-031-0/+0
| | | | | | | | | | | | | | | Submodule src/3rdparty c003ec64..059a95d6: * [Backport] CVE-2025-5283: Use after free in libvpx * [Backport] CVE-2025-5281: Inappropriate implementation in BFCache * [Backport] CVE-2025-5280: Out of bounds write in V8 * [Backport] CVE-2025-5064: Inappropriate implementation in Background Fetch * [Backport] CVE-2025-5065: Inappropriate implementation in FileSystemAccess API * [Backport] CVE-2025-5063: Use after free in Compositing * [Backport] Don't apply /*FALLTHROUGH*/ edit to gperf 3.2 output Pick-to: 6.10 6.9 Change-Id: Ic5ec5af17ef9bbab2da77fbdb469318722b7a93e Reviewed-by: Anu Aliyas <[email protected]>
* Fix narrowing conversions seen on 32bit armKhem Raj2025-06-021-1/+1
| | | | | | | | | | | | | | This issue is seen with clang-19 when compiling for arm32 make clang-19 happier with -Wc++11-narrowing Fixes native_skia_output_device_opengl.cpp:292:47: error: non-constant-expression cannot be narrowed from type ' ↪ uint32_t' (aka 'unsigned int') to 'EGLAttrib' (aka 'int') in initializer list [-Wc++11-narrowing] 292 | EGL_DMA_BUF_PLANE0_PITCH_EXT, nativePixmap->GetDmaBufPitch(0), Pick-to: 6.8 6.9 6.10 Change-Id: I95ba1ab0a37218b6d05324df563efba6d5c39ba2 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Add auto tests for the extension manager APIMartin Negyokru2025-06-022-2/+53
| | | | | | | | | Test QWebEngineExtension and QWebEngineExtenisonManager APIs. Pick-to: 6.10 Task-number: QTBUG-61676 Change-Id: Ib697bdca2ec1d7f9e86ab9ea88e210dfeb2e1780 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Fix ExtensionsClientQt::GetWebstoreUpdateURL()Martin Negyokru2025-06-011-1/+1
| | | | | | | | | Return the actual url instead of using the util method which was causing infinite recursion. Task-number: QTBUG-61676 Change-Id: Ib18d8fa1651bc924522bcb8b3a163241e5c027dc Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Update ChromiumPeter Varga2025-05-301-0/+0
| | | | | | | | | | Submodule src/3rdparty 81d6bcf3..c003ec64: * Add Extension WebUI Fix wrong hash of the previous update. Change-Id: Ie068efa75e91ba86893f2078b17210523c9485dd Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Add support for extension WebUIAnu Aliyas2025-05-3010-15/+301
| | | | | | | | | The WebUI can be accessed using the URL chrome://extensions This will list all the enabled and disable extensions and also provides a means to load extensions. Change-Id: Iddd61a858d100f292f7214e53a1ea753228af0b5 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Add Windows specific driver information to compositor logPeter Varga2025-05-301-0/+21
| | | | | | | | Pick-to: 6.9 Task-number: QTBUG-134746 Change-Id: I56dbc7ffe8ed4c3b689bd3c8ffcbb4feae28a7d2 Reviewed-by: Kaloyan Chehlarski <[email protected]> Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Add API for extension managementMartin Negyokru2025-05-2933-5/+1654
| | | | | | | | | | | | | | | Introduce QWebEngineExtensionManager and QWebEngineExtensionInfo. The manager has methods to load and install Chrome extensions from the filesystem. QWebEngineExtensionInfo provides information about a loaded extension. The current state of our js extension API support is very limited meaning most of the extensions downloaded from Chrome extension store won't work. Adding support for these APIs will be done in followup patches. Fixes: QTBUG-118452 Task-number: QTBUG-61676 Change-Id: I017ad5e8d2ba963afbd2f31ac36fee9451a951bd Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Update ChromiumAnu Aliyas2025-05-281-0/+0
| | | | | | | | | | | | Submodule src/3rdparty 23ba139b..81d6bcf3: * Add Extension WebUI * [fixup] Fix QtWebEngine build on Windows * [angle][vulkan] Fix detection of libvulkan with QtWebEngine * [fixup] Fixes for jumbo build * [fixup] Fix QtWebEngine build on Windows Change-Id: Id34e7451e306a7410f1869a4bd46c5d8db416702 Reviewed-by: Michael Brüning <[email protected]>
* Update ChromiumMichael Brüning2025-05-282-1/+1
| | | | | | | | | | | | | | | Submodule src/3rdparty 23ba139b..2001f9c8: * [Backport] CVE-2025-4609: Incorrect handle provided in unspecified circumstances in Mojo * [Backport] Fixup for bugs 414858409 and 413080347 * [Backport] Security bug 413080347 * [Backport] Security bug 414858409 (2/2) * [Backport] Security bug 414858409 (1/2) * [Backport] CVE-2025-4664: Insufficient policy enforcement in Loader * [Backport] CVE-2025-3277 Task-number: QTBUG-136993 Change-Id: I25112b25c357b2d1e31b2017d6aca11a90d40476 Reviewed-by: Michal Klocek <[email protected]>
* Add API for providing additional CA certificatesKai Uwe Broulik2025-05-2711-5/+118
| | | | | | | | | | This allows to provide additional certificates that are considered when verifying a certificate. This is done by the cert verifier downstream of the platform-specific cert store. Fixes: QTBUG-50586 Change-Id: Ie90547f1013f22f994aaff536fadf906a44a88ef Reviewed-by: Moss Heim <[email protected]>
* Remove custom Content-Type parsing code from URLRequestCustomJobProxyKaloyan Chehlarski2025-05-221-14/+3
| | | | | | | | | | We don't need to be parsing Content-Type headers ourselves, and the existing code won't parse the charset correctly in all cases. Instead, the parsing is now done through net::HttpUtil::ParseContentType(). Pick-to: 6.9 6.8 Change-Id: I94054a8fc1aa3a2b9f8c504e194530719ccdcc11 Reviewed-by: Anu Aliyas <[email protected]>
* Remove usage of deprecated Q_OS_OSX macroKaloyan Chehlarski2025-05-222-2/+2
| | | | | Change-Id: Icfb0373922e936de77715915dd1bc14cad38e067 Reviewed-by: Peter Varga <[email protected]>
* Client Hints: Improve version listsSzabolcs David2025-05-225-15/+74
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are several issues affecting Sec-CH-UA and -Full-Version-List, because the general algorithm which extends and shuffles these lists was not used in WebEngine. At the current version of Chromium we can't use the corresponding user agent utils functions, because they only allow one extra brand/version pair besides the two generated (Chromium and Not-A-Brand) ones. This change implements a simplified method to extend and shuffle the version lists to follow the behavior of Chromium and support more than three elements. QTBUG-133799: The order of brands and versions are still not customizable by the API user, but it is permutated in each major version of Chromium to comply with the standards. To allow customization of the order seems to be impossible without changing our public API. QTBUG-133708: The missing values of Sec-CH-UA are generated from the full version list, not customizable individually. This way it keeps the same values and the same algorithmically generated order as the full version list. Task-number: QTBUG-133711 Task-number: QTBUG-133708 Task-number: QTBUG-133777 Task-number: QTBUG-133799 Change-Id: I96f214ce54190666a34779130a04b56f600abef7 Reviewed-by: Peter Varga <[email protected]> Reviewed-by: Moss Heim <[email protected]>
* Ignore QInputMethodEvent::MimeDataKaloyan Chehlarski2025-05-221-0/+3
| | | | | | | | | Introduced with 2a9444920bcd2f5d1832971bd6275ebdc5515546 We need the version checks to support building on top of older Qt versions. Change-Id: Ifddf8a194a23233eeab61111380dc62ce407f6e7 Reviewed-by: Tor Arne Vestbø <[email protected]>
* Create EGLImage with eglCreateDRMImageMESA() for exporting dma_bufPeter Varga2025-05-212-91/+16
| | | | | | | | | | | | | | | | This simplifies the code because it is not needed to create OpenGL texture to allocate buffer. This way we can get rid of creating a temporary OpenGL context and swapping EGLSurface. Moreover, eglCreateImage() does not guarantee that the buffer is shareable thus certain GPU drivers may fail to export. Pick-to: 6.9 Fixes: QTBUG-136257 Done-with: Jan Palus Change-Id: Ie72d052a2a8b1a41bebf0eab8a4928d38c8fc864 Reviewed-by: Allan Sandfeld Jensen <[email protected]> Reviewed-by: Jan Palus <[email protected]>
* Partial reland of [CMake] Treat QtWebEngineProcess as app targetMichael Brüning2025-05-191-16/+17
| | | | | | | | | | | | | | | | The change from a customly installed executable target to a standard installed app target in d73e99f59cd163e1c99a3e45e9f7050922292d2a caused some regression and led to a revert. Partially restore these changes by using qt_internal_add_app, but also using NO_INSTALL and instead keep the logic we had before for installation and for deciding which location debug information should be stored in. Pick-to: 6.9 Fixes: QTBUG-133593 Change-Id: Iac8ae0fd98086e7e486816440eb115dd5cbb23db Reviewed-by: Moss Heim <[email protected]>
* Add more detailed GPU information to logsPeter Varga2025-05-153-4/+119
| | | | | | | | | | | | | | RHI and ANGLE may use different GPUs and this may lead to various errors. Try to detect these cases from log messages. Enable the following logging rules to compare GPUs in use: QT_LOGGING_RULES="qt.webenginecontext=true;qt.webengine.compositor=true" Pick-to: 6.9 Task-number: QTBUG-135786 Change-Id: I1097acf3d20128b259533a3657532d068f244752 Reviewed-by: Moss Heim <[email protected]> Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Update ChromiumPeter Varga2025-05-141-0/+0
| | | | | | | | | | Submodule src/3rdparty 3e23b0d5..23ba139b: * [vulkan] Force to include local third party headers * Adapt AudioContextManagerImpl for WebEngine * [fixup] Fix QtWebEngine build on Windows Change-Id: I836df1e78f7ca772d61bbae7e701f9791382d1c1 Reviewed-by: Michael Brüning <[email protected]>
* Handle invalid screensMartin Negyokru2025-05-121-1/+1
| | | | | | | | | | | | | Fix a rare crash when WEView is stuck on an invalid (disconnected) display. While being on this display we send invalid screen infos to chromium casuing problems later. Try to send the defaults instead. Pick-to: 6.9 Fixes: QTBUG-136481 Change-Id: Id014148d71fbe559a174eabb056f3e19b367ab25 Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Do not force gl-egl ANGLE backend on LinuxPeter Varga2025-05-081-7/+0
| | | | | | | | | | | | | | Let Chromium decide which ANGLE backend to use by keeping "default" setting. The "gl" backend is available since 75b0d12f6 Add "default" and "gl" ANGLE implementation support to Ozone Reportedly, the "gl-egl" backend doesn't work properly with certain GPU drivers under X11. Task-number: QTBUG-135786 Pick-to: 6.8 6.9 Change-Id: I1592e3c480059b0cd17831ba375ff709f00791cc Reviewed-by: Allan Sandfeld Jensen <[email protected]>
* Do pass -isysroot optionally for gn buildMichal Klocek2025-05-061-2/+2
| | | | | | | | | | | | | | With cmake 4.0 changes, we can no longer expect CMAKE_OSX_SYSROOT to be set: https://cmake.org/cmake/help/latest/release/4.0.html#other-changes Therefore make the setting optional for gn, as it should not be required on "modern macOS". Pick-to: 6.9 6.8 Task-number: QTBUG-135621 Change-Id: I48ed72d6e920fec4c395eb04c8a18619e045c1b4 Reviewed-by: Moss Heim <[email protected]>
* Fix deployment of render process on linuxMichal Klocek2025-05-061-0/+9
| | | | | | | | | | | When deployed on linux qwebengineprocess ends in libexec and needs qt.conf otherwise qt libraries prefix render process is unknown and running the process will fail. Pick-to: 6.9 6.8 Change-Id: If44d4689d11eb8a9f25e2aee28ddef73861575ad Reviewed-by: Joerg Bornemann <[email protected]> Reviewed-by: Alexandru Croitor <[email protected]>
* CMake: Utilize CMAKE_VERBOSE_MAKEFILE setting of CMakeMichal Klocek2025-05-061-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | Define CMAKE_VERBOSE_MAKEFILE also affects ninja generator by adding -v if called through cmake interface ie. 'cmake --build .' https://github.com/Kitware/CMake/commit/ce935ebe50926bde199d86fbde4a78974a4043f9 Use the value of CMAKE_VERBOSE_MAKEFILE to determine if gn or chromium part must be built verbosely, in which case append -v to the invocation of ninja. Unify ninja flags setup for gn and chromium part compile calls, so now NINJAFLAGS environment variable applies when building gn itself. Note this change has side effect compared to cmake patch meaning the verbose mode is applied also when calling ninja directly. Done-With: Fab Stz <[email protected]> Pick-to: 6.9 6.8 Fixes: QTBUG-124007 Change-Id: Id30ffc45ffa8ea4b7995d13905c855cbb4bf6407 Reviewed-by: Alexey Edelev <[email protected]>
* Add debug resources for debug buildsMichal Klocek2025-05-065-18/+73
| | | | | | | | | | | | | | | | | | | | | | | | | | | As unofficial builds do not use scrambled message ids for mojo messages, this causes ipc errors, if we run in debug mode. Therefore for debug builds be explicit and do not use scrambled messages, unlike for any other type. As shipping debug resources (without scrambled messages) increases overall installation size by less then 3MB, simply support creating debug resources with javsscript files created without scrambling messages. Initial idea to keep the resource files in sync with qWebEngineProcessd use case (so for only multi config generator with CMAKE_DEBUG_POSTFIX) did not look good. Therefore, keep things aligned with how we handle v8 sanpshot context files for debug, add "debug" postfix to affected resource files if config is debug. Fixes: QTBUG-131897 Pick-to: 6.9 6.8 Change-Id: I34fa4b4842db521c782af4f4f61212c8cf04ddae Reviewed-by: Joerg Bornemann <[email protected]> Reviewed-by: Moss Heim <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-21 13:44:49 +0000