> I'm not sure what I am supposed to "check" on these? Does it mean I
> should copy the stdcall decoration from NtClose onto these?
Yes, those sdcall decoration are same as NtClose.
WfpCloseDPConfigureHandle and WfpRIOChannelClose are just wrapper of
NtClose, implemented as `jmp cs:NtClose`.
__
On Wed, 9 Mar 2022, Jeremy Drake via Mingw-w64-public wrote:
> +WfpCloseDPConfigureHandle ; Check!!! forwards to NtClose in ntdll.dll
> (ordinal 262)
> +WfpRIOChannelClose ; Check!!! forwards to NtClose in ntdll.dll (ordinal 262)
I'm not sure what I am supposed to "check" on these? Does it mean
Signed-off-by: Jeremy Drake
---
mingw-w64-crt/Makefile.in | 51 ---
1 file changed, 26 insertions(+), 25 deletions(-)
diff --git a/mingw-w64-crt/Makefile.in b/mingw-w64-crt/Makefile.in
index 3609a9e6b..b9a69d83f 100644
--- a/mingw-w64-crt/Makefile.in
+++ b/m
and build import library for arm64.
Signed-off-by: Jeremy Drake
---
.../{libarm32 => lib-common}/fwpuclnt.def | 28 +++-
mingw-w64-crt/lib32/fwpuclnt.def | 149 +-
mingw-w64-crt/lib64/fwpuclnt.def | 146 -
mingw-w64-crt/libarm64/Make
It turns out that "cargo" links with fwpuclnt, and efforts to get rust
working for aarch64-pc-windows-gnu have hit the lack of fwpuclnt.a for
arm64.
While hooking that up, updated the def files to versions generated by
gendef against Windows 11 versions of the DLL.
The second commit is the regene
Hey,
I'm confused about the header files and libraries that MinGW-w64
provides? Does it provide just header files (along with certain
libraries like libstdc++) that enable the compiler to link against
Microsoft-provided DLLs (along with some MinGW-specific DLLs)? What is
the relation between t
