November 2025 - Wine-Devel - list.winehq.org

RoResolveNamespace and winmd

by James McDonnell

Hello, I see the winmd File generation work has landed in wine. In order for affinity to run, it needs to map winrt namespaces to winmd files. These are defined in the idl files afaict. I am looking for guidance of looking up this information in RoResolveNamespace. I see in the widl tool we generate the files. I did not find any parser for winmd files. Is there somewhere I should look? Or is this new ground. Would it be acceptable to have an override in the registry that RoResolveNamespace uses such that wine prefixes can customize if needed? Thank you, James

Nov. 6, 2025

Re: Submitting patches to staging

by light gray

There is no valid information anywhere about how COM interfaces are implemented internally for xgameruntime.dll so I had to do a lot of guesswork and I have documented how I went about implementing them within `QueryApiImpl`. Unfortunately as a result, this leads to functions in which I simply have no clue how they behave, what their signature is or what they return. (example: https://github.com/Weather-OS/WineGDK/blob/master/dlls/xgameruntime/GDKComp… ) There's also the matter of NDA'd interfaces such as the Graphics API or the Audio API. There's simply no way for us to implement those but thankfully those tend to be exclusive to Xbox consoles. For Microsoft services, I don't think any approach we use can be upstreamable because it goes against the whole point of the Wine project being MS free. However I would still implement them within WineGDK and ask for user consent if they want Wine to interact with Microsoft services. On Thu, 6 Nov 2025 at 01:33, Paul Gofman <pgofman(a)codeweavers.com> wrote: > I think the common practice in such cases is that the patch is pulled / > sent by someone with the real name and their name in From:, while patch > comment has "Patch by ..." with original author email / pseudonym (or > 'based on patch by' if the patch was modified beyond some formatting > changes. > > But I think it is not clear what is the future of GDK and specifically > game input in upstream Wine. WRT gameinput, AFAIU it doesn't have a stable > API (at least yet) and the games are supposed to ship it (while some indeed > don't). > > WRT xgameruntime.dll, is there any valid source of info for those internal > interfaces details? Separately, when I was once looking at xgameruntime, > the major problem to get any use of its implementation seemed to be linking > the implementation to actual application data game requests through that > (i. e., it must query MS servers for that). I wonder were there any > thoughts on that part? > > > On 11/5/25 15:51, Ty wrote: > > "the crucial nature for me to stay anonymous" > This can be waived if you are willing to pass up your attribution - it > will be re-authored by another non-anonymous user if you request a waiver > to the rule. I have some misgivings about how this is handled (attribution > is important but now isn't the time to discuss that), however it is a > possibility. I have gone this route myself to get some fixes merged in the > past, and is documented on the wiki for contribution guidelines. > > On Tue, Nov 4, 2025 at 3:31 PM light gray <tpapata1386(a)gmail.com> wrote: > >> >> >> On Nov 4, 2025, at 10:28 AM, light gray <tpapata1386(a)gmail.com> wrote: >> >> >> Hi! >> On the condition that I de-anonymize myself, would it be possible for me >> to submit my patches over at https://github.com/Weather-OS/WineGDK to >> wine staging? >> >> My repository fully complies with Wine's cleanroom guidelines, and more >> importantly, I *do not, and under no circumstances,* use AI generated >> code to implement API functionality. I solely rely on tests written and >> compiled within a Windows environment and Microsoft's own documentation. >> >> Best Regards. >> >> >> After careful consideration, unfortunately, both because of my current >> conditions and the crucial nature for me to stay anonymous, I won’t be >> submitting my patches upstream. >> However, my code will remain/become public domain and is still compliant >> with Wine’s cleanroom guidelines. >> >> Thanks a lot for guiding me through this, I wish you the best. >> >> >> > > > > >

Nov. 6, 2025

Introducing the list.winehq.org domain

by Alexandre Julliard

Folks, Just a heads up that we are starting the process of moving the various Wine mailing lists to a new 'list.winehq.org' domain. So for instance the wine-devel list is going to be at <wine-devel(a)list.winehq.org>. This is necessary to make it possible to host the lists on a different server in the future. Sending mail to the existing @winehq.org addresses will still work, so the change should be mostly transparent, but you may see the list.winehq.org domain start creeping up in the mail headers, and may need to adjust your filters. Note that the recommended way is to filter on the List-Id: header; that one is not expected to change. Thank you for your understanding, -- Alexandre Julliard julliard(a)winehq.org

Nov. 6, 2025

Re: Submitting patches to staging

by Paul Gofman

I think the common practice in such cases is that the patch is pulled / sent by someone with the real name and their name in From:, while patch comment has "Patch by ..." with original author email / pseudonym (or 'based on patch by' if the patch was modified beyond some formatting changes. But I think it is not clear what is the future of GDK and specifically game input in upstream Wine. WRT gameinput, AFAIU it doesn't have a stable API (at least yet) and the games are supposed to ship it (while some indeed don't). WRT xgameruntime.dll, is there any valid source of info for those internal interfaces details? Separately, when I was once looking at xgameruntime, the major problem to get any use of its implementation seemed to be linking the implementation to actual application data game requests through that (i. e., it must query MS servers for that). I wonder were there any thoughts on that part? On 11/5/25 15:51, Ty wrote: > "the crucial nature for me to stay anonymous" > This can be waived if you are willing to pass up your attribution - it > will be re-authored by another non-anonymous user if you request a > waiver to the rule. I have some misgivings about how this is handled > (attribution is important but now isn't the time to discuss that), > however it is a possibility. I have gone this route myself to get some > fixes merged in the past, and is documented on the wiki for > contribution guidelines. > > On Tue, Nov 4, 2025 at 3:31 PM light gray <tpapata1386(a)gmail.com> wrote: > > > >> On Nov 4, 2025, at 10:28 AM, light gray <tpapata1386(a)gmail.com> >> wrote: >> >> >> Hi! >> On the condition that I de-anonymize myself, would it be possible >> for me to submit my patches over at >> https://github.com/Weather-OS/WineGDK to wine staging? >> >> My repository fully complies with Wine's cleanroom guidelines, >> and more importantly, I *do not, and under no circumstances,* use >> AI generated code to implement API functionality. I solely rely >> on tests written and compiled within a Windows environment and >> Microsoft's own documentation. >> >> Best Regards. > > After careful consideration, unfortunately, both because of my > current conditions and the crucial nature for me to stay > anonymous, I won’t be submitting my patches upstream. > However, my code will remain/become public domain and is still > compliant with Wine’s cleanroom guidelines. > > Thanks a lot for guiding me through this, I wish you the best. > > > > >

Nov. 5, 2025

Re: Submitting patches to staging

by Ty

"the crucial nature for me to stay anonymous" This can be waived if you are willing to pass up your attribution - it will be re-authored by another non-anonymous user if you request a waiver to the rule. I have some misgivings about how this is handled (attribution is important but now isn't the time to discuss that), however it is a possibility. I have gone this route myself to get some fixes merged in the past, and is documented on the wiki for contribution guidelines. On Tue, Nov 4, 2025 at 3:31 PM light gray <tpapata1386(a)gmail.com> wrote: > > > On Nov 4, 2025, at 10:28 AM, light gray <tpapata1386(a)gmail.com> wrote: > > > Hi! > On the condition that I de-anonymize myself, would it be possible for me > to submit my patches over at https://github.com/Weather-OS/WineGDK to > wine staging? > > My repository fully complies with Wine's cleanroom guidelines, and more > importantly, I *do not, and under no circumstances,* use AI generated > code to implement API functionality. I solely rely on tests written and > compiled within a Windows environment and Microsoft's own documentation. > > Best Regards. > > > After careful consideration, unfortunately, both because of my current > conditions and the crucial nature for me to stay anonymous, I won’t be > submitting my patches upstream. > However, my code will remain/become public domain and is still compliant > with Wine’s cleanroom guidelines. > > Thanks a lot for guiding me through this, I wish you the best. > > >

Nov. 5, 2025

Re: Submitting patches to staging

by light gray

> On Nov 4, 2025, at 10:28 AM, light gray <tpapata1386(a)gmail.com> wrote: > > Hi! > On the condition that I de-anonymize myself, would it be possible for me to submit my patches over at https://github.com/Weather-OS/WineGDK to wine staging? > > My repository fully complies with Wine's cleanroom guidelines, and more importantly, I do not, and under no circumstances, use AI generated code to implement API functionality. I solely rely on tests written and compiled within a Windows environment and Microsoft's own documentation. > > Best Regards. After careful consideration, unfortunately, both because of my current conditions and the crucial nature for me to stay anonymous, I won’t be submitting my patches upstream. However, my code will remain/become public domain and is still compliant with Wine’s cleanroom guidelines. Thanks a lot for guiding me through this, I wish you the best.

Nov. 4, 2025

Re: Submitting patches to staging

by Elizabeth Figura

On Tuesday, 4 November 2025 00:58:19 CST light gray wrote: > Hi! > On the condition that I de-anonymize myself, would it be possible for me to > submit my patches over at https://github.com/Weather-OS/WineGDK to wine > staging? > > My repository fully complies with Wine's cleanroom guidelines, and more > importantly, I *do not, and under no circumstances,* use AI generated code > to implement API functionality. I solely rely on tests written and compiled > within a Windows environment and Microsoft's own documentation. That seems to be a complete understanding of our legal and authorship requirements. We do want to make sure the patches are going in the right direction. Also, we encourage people to at least try to get their patches upstream if they're able. I'd offer comment on the patches in question, but it looks like you're using merges so I'm not sure I'll be able to find all of them. It does look like you're working on the "gameinput" DLL, which I think Rémi Bernon is also working on, so it would be prudent for us to coordinate that first.

Nov. 4, 2025

Submitting patches to staging

by light gray

Hi! On the condition that I de-anonymize myself, would it be possible for me to submit my patches over at https://github.com/Weather-OS/WineGDK to wine staging? My repository fully complies with Wine's cleanroom guidelines, and more importantly, I *do not, and under no circumstances,* use AI generated code to implement API functionality. I solely rely on tests written and compiled within a Windows environment and Microsoft's own documentation. Best Regards.

Nov. 4, 2025

Wine staging 10.18 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.18 (283 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * scrrun: Implement MoveFolder(). * scrrun: Check for null and empty arguments in MoveFolder. * scrrun: Test MoveFolder with already existing destination. * scrrun: Check for non-existant source in MoveFolder(). * scrrun: Check that source is directory in MoveFolder(). * scrrun: Move source dir into destination dir if destination ends with separator in MoveFolder(). * scrrun: Support wildcards in MoveFolder(). * scrrun: Move directories only in MoveFolder(). * scrrun: return path not found error if source ends with path separator in MoveFolder(). * scrrun: Return path not found error if no folders were moved in MoveFolder(). * user32: Implement CascadeWindows. * user32: Implement TileWindows * wineboot: Initialize proxy settings registry key. * ws2_32/tests: Add test for AF_UNIX sockets. Removed (No longer required). * None Added: * None Updated: * vkd3d-latest Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

Nov. 1, 2025