Unable to compile dlib due to some file encoding issue?
ManHinnn0509 opened this issue · 6 comments
What Operating System(s) are you seeing this problem on?
Windows
dlib version
19.24
Python version
3.9.13
Compiler
GCC 11.3.0, MSVC 14
Expected Behavior
Since CUDA and cuDNN was found, I expect to install dlib with CUDA support
Current Behavior
When I run cmake ..
in build
directory, it says "CUDA was found but your compiler failed to compile a simple CUDA program so dlib isn't going to use CUDA." and CUDA is not going to be used in dlib. The error message seems to be related to some file encoding issue? The whole output is very long so I uploaded it as a gist raw file
Steps to Reproduce
cd dlib
mkdir build
cd build
cmake ..
^ The error occurs during in cmake ..
Anything else?
I also tried to build test_for_cuda
and test_for_cudnn
(As mentioned in another issue), test_for_cudnn
has no error but test_for_cuda
has error in cmake --build .
, the output is also very long so I also uploaded it as a gist raw file
Tried to Google this and search it in here but by far couldn't find anything related to this... Please help
I can't say, other than it looks like something in your visual studio or cuda install is broken (i.e. something unrelated to dlib).
I downgraded CUDA from 11.3 to 11.2, CUDA is working because Tensorflow is using my GPU and also upgraded VS2019 but the problem still exists.
I wonder if I can use VS2019 to compile dlib? Because I can't download VS2015 anymore and I plan to re-install VS2019 if it can be used to compile dlib
Yeah VS2019 is fine. As are newer versions of visual studio.
Got it, will try again soon and I will keep things updated in here.
Warning: this issue has been inactive for 38 days and will be automatically closed on 2024-06-27 if there is no further activity.
If you are waiting for a response but haven't received one it's possible your question is somehow inappropriate. E.g. it is off topic, you didn't follow the issue submission instructions, or your question is easily answerable by reading the FAQ, dlib's official compilation instructions, dlib's API documentation, or a Google search.
Notice: this issue has been closed because it has been inactive for 45 days. You may reopen this issue if it has been closed in error.