[Mingw-w64-public] [PATCH] headers: restrict winscard to Desktop builds

It's not allowed in UWP. --- mingw-w64-headers/include/winscard.h | 5 + 1 file changed, 5 insertions(+) diff --git a/mingw-w64-headers/include/winscard.h b/mingw-w64-headers/include/winscard.h index 7373d1915..1ecabb881 100644 --- a/mingw-w64-headers/include/winscard.h +++ b/mingw-w64-heade

[Mingw-w64-public] [PATCH] crt: consistently hide winstorecompat wincrypt API's

The x86 bits version hides them, but not the common version. It should always be hidden as in 9464ea241865f218cdfee9784bb6dc1731a23647. They are now part of WindowsApp.lib but only enabled for desktop builds. Desktop users using libwindowsapp.a or libmincore.a won't be able to use the actual syste

[Mingw-w64-public] [PATCH] crt: add some missing CRT entries

According to the WACK. --- .../lib-common/api-ms-win-crt-filesystem-l1-1-0.def | 5 + mingw-w64-crt/lib-common/api-ms-win-crt-heap-l1-1-0.def | 1 + mingw-w64-crt/lib-common/api-ms-win-crt-stdio-l1-1-0.def | 1 + 3 files changed, 7 insertions(+) diff --git a/mingw-w64-crt/li

[Mingw-w64-public] [PATCH 2/2] crt: remove some API's not officially exported/documented

They are not mentioned in the Windows Application Certification Kit so they should not be used anyway in windowsapp/mincore. --- mingw-w64-crt/lib-common/api-ms-win-core-winrt-error-l1-1-0.def | 1 - mingw-w64-crt/lib32/api-ms-win-core-version-l1-1-1.def | 1 - mingw-w64-crt/lib32/api-ms-

[Mingw-w64-public] [PATCH 1/2] crt: add missing GetFileVersionInfoW in lib32 version-l1-1-1

It's already found in the common version. --- mingw-w64-crt/lib32/api-ms-win-core-version-l1-1-1.def | 1 + 1 file changed, 1 insertion(+) diff --git a/mingw-w64-crt/lib32/api-ms-win-core-version-l1-1-1.def b/mingw-w64-crt/lib32/api-ms-win-core-version-l1-1-1.def index 9a6bea936..4ed3c5966 10064

[Mingw-w64-public] [PATCH] headers: allow GetNumaHighestNodeNumber in Win10 19H1 UWP builds

It is not allowed in older SDK. It won't compile or won't link. The target DLL will likely not have the function, so it should not be used when targetting older Windows 10 versions in UWP mode. --- mingw-w64-headers/include/systemtopologyapi.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion

Re: [Mingw-w64-public] [PATCH] configure: Use ucrt for msvcrt by default.

On Thu, 8 Jun 2023, LIU Hao wrote: There are also builds with clang, but clang expects UCRT anyway This statement is untrue. * MSYS2: https://github.com/msys2/MINGW-packages/blob/bf2ba8f4bba3d14fdaa2572cffb4abd4e6791246/mingw-w64-crt-git/PKGBUILD#L65 Yes, the msys2 "clang*" environments a

Re: [Mingw-w64-public] [PATCH 1/2] headers: Add wia.idl

> It should be easy to add them to Wine. Never experienced that "easy"-ness. > Compatibility with Windows SDK seems better, otherwise we'd miss support > for things like "#include ". OK, I shall try. ___ Mingw-w64-public mailing list Mingw-w64-public

Re: [Mingw-w64-public] [PATCH] configure: Use ucrt for msvcrt by default.

I agree that those are valid concerns. However, there is little we can do about it and it's unlikely to change over time. Do we want msvcrt-os to remain the default forever? For your information, this is a non-exhaustive list of distributions that do not specify `--with-default-msvcrt` and will

Re: [Mingw-w64-public] [PATCH 1/2] headers: Add wia.idl

On 6/7/23 19:46, Biswapriyo Nath wrote: Do we need to reimplement 'wia.idl', instead of importing 'wia_lh.idl' and 'wia_xp.idl' from Wine? wia_lh.idl and wia_xp.idl in wine are missing many declarations. It should be easy to add them to Wine. Besides, wia_xp.h is just a stripped down vers

Re: [Mingw-w64-public] [PATCH 1/2] headers: Add wia.idl

> Do we need to reimplement 'wia.idl', instead of importing 'wia_lh.idl' and > 'wia_xp.idl' from Wine? wia_lh.idl and wia_xp.idl in wine are missing many declarations. Besides, wia_xp.h is just a stripped down version of wia_lh.h in Windows SDK. So, adding just wia.idl is good enough. _

Re: [Mingw-w64-public] [PATCH] Define FLS_MAXIMUM_AVAILABLE as 4080 for WIN10_19H1

Yes, looks good! Thanks, Luca Da: LIU Hao Inviato: mercoledì, giugno 7, 2023 5:07:07 PM A: Luca Bacci ; mingw-w64-public@lists.sourceforge.net Oggetto: Re: [Mingw-w64-public] [PATCH] Define FLS_MAXIMUM_AVAILABLE as 4080 for WIN10_19H1 在 2023-06-07 22:47, Luca

Re: [Mingw-w64-public] [PATCH] Define FLS_MAXIMUM_AVAILABLE as 4080 for WIN10_19H1

在 2023-06-07 22:47, Luca Bacci 写道: Indeed it's quite a strange macro, reminds me of https://devblogs.microsoft.com/oldnewthing/20160613-00/?p=93655 The macro `TLS_MINIMUM_AVAILABLE` also does not make much sense because the indexes 0, 1, 4, 16 and 64 are pre-allocated and will be skipped by `

Re: [Mingw-w64-public] [PATCH] Define FLS_MAXIMUM_AVAILABLE as 4080 for WIN10_19H1

Typo there: *0x0602* is Windows 8 Luca Inviato da Outlook per Android From: Luca Bacci Sent: Wednesday, June 7, 2023 4:47:43 PM To: LIU Hao ; mingw-w64-public@lists.sourceforge.net Subject: Re: [Mingw-w64-public] [PATCH] Define FLS_MAXIM

Re: [Mingw-w64-public] [PATCH] Define FLS_MAXIMUM_AVAILABLE as 4080 for WIN10_19H1

Indeed it's quite a strange macro, reminds me of https://devblogs.microsoft.com/oldnewthing/20160613-00/?p=93655 :) While writing a few tests for fiber local storage I found that the Windows SDK had a different value, so thought about updating the mingw-w64 headers. But actually I don't have an

Re: [Mingw-w64-public] [PATCH 2/2] headers: Allow SetDllDirectoryW/A API in Win10 19H1 UWP builds

在 2023-06-07 15:46, Steve Lhomme 写道: The documentation doesn't say it's allowed but they are allowed by the Windows Application Certification Kit and the 18362 Windows SDK. It is not allowed in older SDK. It won't compile or won't link. The target DLL [1] will likely not have the function, so it

Re: [Mingw-w64-public] [PATCH 1/2] headers: Add wia.idl

在 2023-06-07 01:32, Biswapriyo Nath 写道: From da3f44c338b40c51d0f289d8aebcaf45e6770ce8 Mon Sep 17 00:00:00 2001 From: Biswapriyo Nath Date: Tue, 6 Jun 2023 21:46:02 +0530 Subject: [PATCH 1/2] headers: Add wia.idl Tested withhttps://learn.microsoft.com/en-us/windows/win32/wia/-wia-creating-a-wia

Re: [Mingw-w64-public] [PATCH] crt: Add a missing dependency for libmincore.a

在 2023-06-07 14:54, Martin Storsjö 写道: 95d1c1045537158542424570a9ec57a543052aa1 included libapi-ms-win-core-heap-l1-1-0.a into libmincore.a, but didn't add the necessary dependency in Makefile.am. Signed-off-by: Martin Storsjö --- mingw-w64-crt/Makefile.am | 1 + 1 file changed, 1 insertion(

Re: [Mingw-w64-public] [PATCH] Define FLS_MAXIMUM_AVAILABLE as 4080 for WIN10_19H1

在 2023-06-06 21:26, Luca Bacci 写道: Hi! Right, the Windows SDK defines FLS_MAXIMUM_AVAILABLE unconditionally, let's do the same here. Sorry here was some confusion. As this value has been increased only since Windows 10, there really should be an `#if` check. I was a bit uncertain about whic

Re: [Mingw-w64-public] [RFC] Make Windows 10 DLLs closer to documentation

On 2023-06-07 15:35, LIU Hao wrote: 在 2023-06-07 13:55, Steve Lhomme 写道: Indeed. I made a tool (private as I'm not sure how legally safe it is) to generate the .def files from the WACK XML files. I used it to find which DLLs are needed to export some functions. However, it seems that this expo

Re: [Mingw-w64-public] [RFC] Make Windows 10 DLLs closer to documentation

在 2023-06-07 13:55, Steve Lhomme 写道: Indeed. I made a tool (private as I'm not sure how legally safe it is) to generate the .def files from the WACK XML files. I used it to find which DLLs are needed to export some functions. However, it seems that this export doesn't match any version of Window

Re: [Mingw-w64-public] [RFC] Make Windows 10 DLLs closer to documentation

Hi, On 2023-06-07 7:55, Steve Lhomme wrote: Hi, On 2023-06-06 18:16, LIU Hao wrote: Attached are some patches about APIs yesterday.    3) The change against `api-ms-win-security-cryptoapi-l1-1-0.def` should   probably be reverted, as in 9464ea241865f218cdfee9784bb6dc1731a23647. The

Re: [Mingw-w64-public] [RFC] Make Windows 10 DLLs closer to documentation

On 2023-06-07 11:47, LIU Hao wrote: 在 2023/6/7 13:55, Steve Lhomme 写道:    1) `GetFileVersionInfoW` isn't mentioned anywhere. According to its   documentation [3] it should be imported from   `api-ms-win-core-version-l1-1-0.dll` but that DLL exports no such   function. I think you m

Re: [Mingw-w64-public] [RFC] Make Windows 10 DLLs closer to documentation

在 2023/6/7 13:55, Steve Lhomme 写道:    1) `GetFileVersionInfoW` isn't mentioned anywhere. According to its   documentation [3] it should be imported from   `api-ms-win-core-version-l1-1-0.dll` but that DLL exports no such   function. I think you mean api-ms-win-core-version-l1-1-1. T

[Mingw-w64-public] [PATCH 1/2] headers: enabled LoadLibraryEx flags in Win10 19H1 UWP builds

--- mingw-w64-headers/include/libloaderapi.h | 48 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/mingw-w64-headers/include/libloaderapi.h b/mingw-w64-headers/include/libloaderapi.h index 00aa50f2a..6a5f59ed4 100644 --- a/mingw-w64-headers/include/libload

[Mingw-w64-public] [PATCH 2/2] headers: Allow SetDllDirectoryW/A API in Win10 19H1 UWP builds

The documentation doesn't say it's allowed but they are allowed by the Windows Application Certification Kit and the 18362 Windows SDK. It is not allowed in older SDK. It won't compile or won't link. The target DLL [1] will likely not have the function, so it should not be used when targeting olde