You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library appears to have some support for compiling under WDM when developing Windows Kernel drivers.
However, I've noticed that some CRT headers are still included, specifically, in wistd_functional.h we include <new.h> and <intrin.h>, the question is, are those normal headers to be included? Yes, they're part of the WDK under the km/ folder, but is it truly okay to include them?
Does anyone else know if it's a good idea to use this library in windows kernel projects anyway? We want to take advantage of the unique_any functionality, which appears to work. But I'm worried about any side effects or extra "baggage" that including these CRT-like files may bring.
The text was updated successfully, but these errors were encountered:
This library appears to have some support for compiling under WDM when developing Windows Kernel drivers.
However, I've noticed that some CRT headers are still included, specifically, in
wistd_functional.h
we include<new.h>
and<intrin.h>
, the question is, are those normal headers to be included? Yes, they're part of the WDK under thekm/
folder, but is it truly okay to include them?Does anyone else know if it's a good idea to use this library in windows kernel projects anyway? We want to take advantage of the
unique_any
functionality, which appears to work. But I'm worried about any side effects or extra "baggage" that including these CRT-like files may bring.The text was updated successfully, but these errors were encountered: