-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Example programs fail compilation due to HANDLE being undefined #338
Comments
Perhaps you could help me out on where to get this type definition from. Have a look at this:
It's some kind of Win32 memory handle. Which file is it coming from? Or - what type is it, actually? |
Also... could you try replacing |
Ok, so I found that When I replace
When I keep the |
These are all separate issues :-P ... which need to be filed and handled separately. If it's too much of a hassle for you then I'll do it. Anyway, my workaround for |
I see you beat me to it, I believe you've already reported these issues separately yourself. Thank you for the swift assistance! |
@Q-Minh : Actually, not really. The 1st, 4th and 5th issues are unfiled... |
Using VS2019, CMake 3.18.4 and CUDA Toolkit 11.4, I get a compilation error when trying to build the examples from this repository.
Essentially, in
cuda/api/virtual_memory.hpp
, the typeHANDLE
is undefined. There might be some#include
directive missing somewhere such that the WinAPI'sHANDLE
is not defined. I tried a quick fix by adding#include <windows.h>
on top ofcuda/api/virtual_memory.hpp
, but now a macro namedmax
gets defined, such that the expressionstd::numeric_limits<int>::max()
is ill-formed when used incuda/nvrt/program.hpp
, because themax
substring in it gets string-replaced by the preprocessor to something else.I've successfully compiled all the samples from the CUDA Toolkit v11.4 with VS2019, so I know I have a CUDA 11.4 capable environment.
The
cuda-api-wrappers
example targets that I've tested with failed compilations aredevice_management
andarray_management
. Other targets also have the same problem.The text was updated successfully, but these errors were encountered: