cppwin32
wil
cppwin32 | wil | |
---|---|---|
15 | 14 | |
395 | 2,457 | |
- | 0.7% | |
5.5 | 7.9 | |
over 3 years ago | 11 days ago | |
C++ | C++ | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cppwin32
-
MSVC C++23 Update
I would imagine something like https://github.com/microsoft/cppwin32 would maybe be an easier way forward for that?
-
TIL we can prevent macro invocation by placing the function name in parentheses
no, Microsoft has rewritten the windows API in C++ I think https://github.com/microsoft/cppwin32
-
A brief interview with Tcl creator John Ousterhout
An official work in progress Windows binding, still far behind of what C# existing bindings are capable of, or legacy toolkits like MFC.
Also given how the team has managed C++/CX transition to C++/WinRT with lesser tooling stuck on C++17, dropped Modern C++ bindings [0][1], before going into other shinny thing, I wonder how long they will keep at it.
[0] - https://blogs.windows.com/windowsdeveloper/2021/01/21/making...
[1] - https://github.com/microsoft/cppwin32
-
VS2022 how to make Windows C++ (like VB) program
If you want to use the old tooling, your C++ is going to be very "C with classes," and it's going to use a lot of weird datatypes that don't feel very C++ at all. Microsoft had a project for wrapping the Windows API in idiomatic C++, but appear to have abandoned it. If you choose to go down this road, Charles Petzold's Programming Windows is the book to get. Yes, it's 25 years old, but all the new stuff is just new COM controls (which you can look up in the API documentation)--the fundamentals of making a Windows API program work seriously have not changed.
-
Windows API as a C++ module ?
Even Rust has a native projection of the windows API (which is actually pretty usable). This projection has the same roots as the C++ projection mentioned by u/amnesiac0x07C5. So I don't believe macros are a blocker here.
-
Win32 strings
See : https://github.com/microsoft/cppwin32
-
Wanting to get started
Microsoft have recently put decent effort into making the Windows APIs more accessible to C++ users. One of these efforts is called C++/WinRT, and it specifically targets applications intended for "modern" Windows (Windows 8 and later). There's another effort underway at Microsoft for making the older Win32 API more C++-friendly, but it isn't documented nearly as well.
-
How to use C++ HANDLE event
There is a similar project for C++, but it sadly seems to be dead already. The last commit was one year ago.
-
[Belay the C++] windows.h breaks the STL (and my will to live)
not that hard to wrap windows.h and undef the annoying stuff, and only a handful of files in your codebase will include it anyway. on the other hand stuff like this looks extremely worse and exactly like the kind of c++ that is hard banned in gamedev codebases
-
Microsoft is working on making the Win32 api available for use in modern C++
They are, actually, it's linked from the article: https://github.com/microsoft/cppwin32
wil
-
C-Macs – a pure C macOS application
Even then, MFC and C++/CX were the only productive ways to use it from Microsoft SDKs.
.NET isn't as convenient as VB 6 was, fully embracing COM as the VBX replacement model, technically introduced in VB5, but still some stuff was lacking.
Then there is Delphi and C++ Builder.
It beat me that having doubled down on COM since how Longhorn went down, and Windows team getting their way doing avoiding .NET to take over, they hardly managed to create nice tooling as the competition.
Editing IDL files with a Notepad like experience, manually merging generated code, and a couple of frameworks that barely go beyond yet another way to do AddRef/Release/QueryInterface and aggregation.
Meanwhile D-BUS, XPC and AIDL, provide much better dev experience.
Pity that Borland products are kind of tainted due to mismanagement decisions, otherwise maybe fixing COM dev experience would already been seriously taken by VS team.
Ah, nowadays WIL is probably the best approach when having only to consume COM.
https://github.com/microsoft/wil
-
ntoskrnl7/crtsys: C/C++ Runtime library for system file (Windows Kernel Driver)
Have a look at WIL for a C++ library used by Microsoft themselves, including kernel development.
-
I'm thinking about using a struct to hold allocated memory and guaranteeing it will be released when the struct goes out of scope, as an alternative to smart pointers. What do you think?
I'm digging for more information and it looks like Microsoft's created a way to handle the problems I'm trying to address with this: https://github.com/Microsoft/wil/wiki/RAII-resource-wrappers
-
Unwrapping WinUI3 for C++
Since we are on this subject, those that need a nice C++ library to deal with COM in VC++, are better served with WIL.
-
RISC-V J extension – Instructions for JITs
Not since Vista.
https://docs.microsoft.com/en-us/cpp/build/reference/kernel-...
> Creates a binary that can be executed in the Windows kernel. The code in the current project gets compiled and linked by using a simplified set of C++ language features that are specific to code that runs in kernel mode.
And then there is WIL, https://github.com/microsoft/wil
https://community.osr.com/discussion/291326/the-new-wil-libr...
> First off, let me point out that this library is used to implement large parts of the OS. There are hundreds of developers here who use it. So unlike, uh, some other things that get tossed onto github, this project is not likely to wither and die tomorrow.
> There are, however, only a handful of kernel developers working on the library, so the kernel support has been coming along much slower. I'd like to expand the existing kernel features in depth ....
-
ToaruOS 2.0
> Plus C++ standard library can't be used anyway and auto pointers aren't really that much of a concern at the kernel level
https://github.com/microsoft/wil
"Ah, but that isn't used on the Windows kernel" would be the expected reply, well
https://community.osr.com/discussion/291326/the-new-wil-libr...
"Microsoft's toolchain does not ship a copy of the STL that works in kernel mode. Partly this is because the kernel's CRT doesn't support C++ exceptions. (And partly this is because I/O is wildly different in kernel, so you'd have to rewrite the implementation of all the I/O libraries.)
But for kernel developers, wil ships a subset of an STL implementation. To avoid conflicting with the real STL, it's available under the wistd namespace. The rule of thumb is that wistd::foo is a drop-in replacement for std::foo."
-
Linux Sucks 2021 – The End of Linux Is Nigh
Windows is a mix of legacy C code, which started to be migrated into C++ around the Vista time (hence /kernel in VC++) and .NET/COM (WinRT is basically COM with some extras).
Modern kernel code makes use of WIL.
https://github.com/microsoft/wil
- Away from Exceptions: Errors as Values
- Windows Implementation Libraries (WIL)
- Finding Windows HANDLE leaks, in Chromium and others
What are some alternatives?
winapi - Windows API declarations without <windows.h>, for internal Boost use.
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
toaruos - A completely-from-scratch hobby operating system: bootloader, kernel, drivers, C library, and userspace including a composited graphical UI, dynamic linker, syntax-highlighting text editor, network stack, etc.
STL - MSVC's implementation of the C++ Standard Library.
stlkrn - C++ STL in the Windows Kernel with C++ Exception Support
win32metadata - Tooling to generate metadata for Win32 APIs in the Windows SDK.
go-figure - Prints ASCII art from text.
crtsys - C/C++ Runtime library for system file (Windows Kernel Driver) - Supports Microsoft STL
EA Standard Template Library - EASTL stands for Electronic Arts Standard Template Library. It is an extensive and robust implementation that has an emphasis on high performance.