-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: Support for UCRT? #619
Comments
Lets separate the two things: switching from Stop using As for using/switching to Now regarding re-using code. There'are 4 different backends, not just Windows and POSIX. The only code that can really be re-used is mostly not related too strigns conversions (e.g. hid_enumerate or hid_error). Most of other code is platform-specific and won't be re-used anyway.
There're mostly legacy reasons for that - Alan Ott chose to use it at the time and we can't "just change" it as of this moment. |
In the last few years more recent builds of Windows 10 have gained better and better support for UTF8. It may be possible to switch to the char based APIs for the Windows backend and switch to linking to UCRT as well. This would, in theory, enable for more code to be reused between the Windows backend and POSIX systems.
If this were to be done, we could probably also switch to using char strings exclusively in the public API of
hidapi
. I found it strangehidapi
even uses wide characters, and I assume it is related to the Windows backend.The text was updated successfully, but these errors were encountered: