- Wine-GitLab - list.winehq.org

[PATCH v4 0/1] MR10362: vbscript: Support chained call syntax like dict.Keys()(i).
by Francis De Brabandere (＠francisdb) March 24, 2026

March 24, 2026

Treat '(' after tEMPTYBRACKETS as an argument list opener in the lexer, so that expressions like GetArr()(0) or dict.Keys()(i) parse correctly. Also dereference VT_BYREF|VT_VARIANT results in vcall so chained indexing on call results works at runtime. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=58051 This includes some of the work done in !10308, preferably that one is merged first. -- v4: vbscript: Support chained call syntax like dict.Keys()(i). https://gitlab.winehq.org/wine/wine/-/merge_requests/10362

2 3

[PATCH v3 0/1] MR10384: vbscript: Allow hex literals with excess leading zeros.
by Francis De Brabandere (＠francisdb) March 24, 2026

March 24, 2026

Windows allows any number of leading zeros in hex literals (e.g. &H000000031 = 49). Wine rejected literals with more than 8 hex digits regardless of value. Fix by skipping leading zeros before counting significant digits, so that only actual 32-bit overflow is rejected. -- v3: vbscript: Allow hex literals with excess leading zeros. https://gitlab.winehq.org/wine/wine/-/merge_requests/10384

2 2

[PATCH 0/1] MR10437: ntoskrnl.exe/tests: Fix stack use-after-free of OVERLAPPED.
by Yuxuan Shui (＠yshui) March 24, 2026

March 24, 2026

The ioctls started in `test_cancel_thread` complete only after the function has already returned, thus the OVERLAPPED objects needed have become invalid. Make them global variables. This should be fine since we only start the next test thread after we have completed the previously started IO operations. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10437

3 3

[PATCH v3 0/2] MR10438: configure: fail early on invalid Gradle/SDK
by Twaik Yont (＠twaik) March 24, 2026

March 24, 2026

This change is motivated by the long-standing issue that most Linux distributions ship an outdated Gradle, which is often too old for modern Android builds. In typical Android projects this is solved by using the Gradle wrapper, which ensures a compatible Gradle version is downloaded and used automatically. However, Wine cannot rely on the Gradle wrapper for this purpose, and integrating automatic downloads into the build system is not acceptable, since the build process must not fetch external resources. As a result, Gradle and the Android SDK effectively become external prerequisites that must be provided by the user or by higher-level build scripts. Previously, missing or outdated dependencies would only surface later during the build, often resulting in confusing or hard-to-diagnose errors. This change makes these requirements explicit and enforces them at configure time: - `gradle` is detected, its version is checked, and the resolved path is cached. - `ANDROID_HOME` is required and validated against the expected SDK layout. - A minimal sanity check ensures that a usable `build-tools` installation is present. This allows the build to fail early with clear error messages if the environment is not properly set up, instead of failing deep inside the Gradle build. Additionally, `GRADLE` and `ANDROID_HOME` are cached by configure, so they do not need to be re-specified when invoking make or even present in environment. -- v3: wineandroid: print hint for full APK build when using dummy target https://gitlab.winehq.org/wine/wine/-/merge_requests/10438

2 3

Re: [PATCH v2 0/1] MR10352: cabinet: Add stubs for compressor/decompressor
by Chris Kadar (＠nspitko) March 24, 2026

March 24, 2026

On Tue Mar 24 11:40:24 2026 +0000, Nikolay Sivov wrote: > Could you check which algorithm this game is using? We have at least > some MSZIP code scattered around, and maybe this could be consolidated > at some point (not in this MR obviously). It's using algorithm 4, which appears to be "XPRESS compression algorithm with Huffman encoding". -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10352#note_133550

1 0

[PATCH 0/1] MR10438: configure: fail early on invalid Gradle/SDK
by Twaik Yont (＠twaik) March 24, 2026

March 24, 2026

This change is motivated by the long-standing issue that most Linux distributions ship an outdated Gradle, which is often too old for modern Android builds. In typical Android projects this is solved by using the Gradle wrapper, which ensures a compatible Gradle version is downloaded and used automatically. However, Wine cannot rely on the Gradle wrapper for this purpose, and integrating automatic downloads into the build system is not acceptable, since the build process must not fetch external resources. As a result, Gradle and the Android SDK effectively become external prerequisites that must be provided by the user or by higher-level build scripts. Previously, missing or outdated dependencies would only surface later during the build, often resulting in confusing or hard-to-diagnose errors. This change makes these requirements explicit and enforces them at configure time: - `gradle` is detected, its version is checked, and the resolved path is cached. - `ANDROID_HOME` is required and validated against the expected SDK layout. - A minimal sanity check ensures that a usable `build-tools` installation is present. This allows the build to fail early with clear error messages if the environment is not properly set up, instead of failing deep inside the Gradle build. Additionally, `GRADLE` and `ANDROID_HOME` are cached by configure, so they do not need to be re-specified when invoking make or even present in environment. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10438

2 1

[PATCH v2 0/7] MR10009: mf/topology_loader: Refactor the topology loader and fix a few test failures.
by Conor McCarthy (＠cmccarthy) March 24, 2026

March 24, 2026

This changes the functionality relatively little, but the refactoring will allow greater changes in a followup MR which will fix more tests. -- v2: mf/topology_loader: Load the branch up connection method only for source nodes. mf/topology_loader: Use the branch connection context for down nodes. mf/topology_loader: Set the branch upstream node media type if not a source node. mf/topology_loader: Introduce a branch connection context. mf/topology_loader: Delete unused struct connect_context. mf/topology_loader: Do not create a new branch list containing downstream nodes. mf: Trace additional topology details. https://gitlab.winehq.org/wine/wine/-/merge_requests/10009

4 12

[PATCH 0/6] MR10364: dinput: Add support for generating consistent guidInstance values for devices.
by Connor McAdams (＠cmcadams) March 24, 2026

March 24, 2026

This MR adds support for creating `guidInstance` values for joystick devices in a way that matches native behavior. Our current method of creating a `guidInstance` value uses the device's rawinput handle, which changes each time a controller is plugged in. Fixes a bug in Rocket League where a controller plug/unplug cycle results in a new controller being detected each time. The process is like this: - Controller is connected, the game gets its `guidInstance` value from `EnumDevices()`, stores it and associates it with player 1. - Controller is disconnected. - The same controller is reconnected, the game calls `EnumDevices()`, and finds a new `guidInstance` value. - It then assumes this is a new controller, creates a new player, and behaves as though player 1's controller is unplugged. This MR implements `guidInstance` in a way that matches native, and ensures that the `guidInstance` value remains consistent. Doing things this way also makes it easier to add support for `DIPROP_JOYSTICKID` and `GUID_Joystick` in a future MR. I've implemented those in a branch [here](https://gitlab.winehq.org/cmcadams/wine/-/tree/WIP/dinput-instance-gu… using this system. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10364

3 15

Re: [PATCH v2 0/14] MR10349: opengl32: Implement wglGetProcAddress on the client side.
by Rémi Bernon March 24, 2026

March 24, 2026

> Specs for most of them are available, so we know they don't add new commands. They are just not a part of the official registry. `GL_ATI_texture_compression_3dc` has no spec. `GL_APPLE_packed_pixels` had a unofficial one but it's now difficult to find, all the tokens it defines are also already defined in OpenGL 1.2, so I don't think exposing it is going to make any difference. The same reasoning as above wrt platform extensions applies for it as well. > It is part of the extension strings exposed by Mesa. In any case, we could filter it if there is an actual benefit, but I do not see why we would need to. What exactly looks wrong to you? GLSL extensions aren't supposed to be exposed there, unless they have a matching GL extension to add tokens / commands or change GL behavior. This one doesn't do any of that on the GL side, and I believe it is not meant to be exposed in GL_EXTENSIONS. This leaves `GL_EXT_texture_edge_clamp` / `GL_EXT_texture_rectangle` / `GL_MESA_texture_signed_rgba` with unofficial specs and which we can expose, yes. And then there are more spec-less extensions that are exposed by native drivers. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10349#note_133537

1 0

Re: [PATCH v2 0/14] MR10349: opengl32: Implement wglGetProcAddress on the client side.
by Rémi Bernon March 24, 2026

March 24, 2026

On Fri Mar 20 09:47:23 2026 +0000, Jacek Caban wrote: > Yes, it's about those two extensions mostly. I could maybe disable > others, but why? They are well handled by make_opengl. I also don't see > how being similar to other extensions changes anything. The issue I see is that exposing extensions that aren't expected to be there by applications have a chance of confusing them. It's possible for instance that an application check for GL_ANGLE extension and decide to enable some ANGLE specific rendering mode. On Windows the AMD drivers do not support those extensions, but on Wine most of the time Mesa is used for AMD GPUs and they would be exposed. The same logic applies to platform specific extensions like GL_APPLE or other platform extensions that are currently filtered out. Sure `make_opengl` could support some of them, and sure, GL extensions aren't restricted and some other driver could implement them including on Windows, but it's not the case in practice and passing them through creates a runtime environment that differ from any possible native environment Windows applications have been developed for. Filtering out extensions which aren't, or very rarely, there on Windows is less likely to break anything, because no application is expected to benefit from them anyway. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10349#note_133536

1 0