I am trying to build a cuda program but it is giving me error as cutil64D.lib file not found.
I tried to build the file by opening the cutil_vs2008.sln solution file in vs 2008 and build it,but still I am not getting the cutil64D.lib.
Please suggest me something.
Thanks
You need to set the platform to x64 and the mode to debug when building cutil_vs2008.sln.
CUTIL is a simple utility library designed for use in the CUDA SDK samples, not part of CUDA.
You can build the solution under %SDK_Dir%\C\common\cutil_vs2008.sln by setting platform to x64 and the mode to debug, then you will get what you want under %SDK_Dir%\C\common\lib\x64.
But, if you've already had this lib under some directory, setting platform and mode wrong could invite "can not find lib" error above.
Related
I hope this is not a duplicate, as I have been searching the web for a while looking for solutions to my issue.
So, I am working in this C++ project from the lab I work at which works just fine in CLion and Visual Studio. However, I'm trying to run it in my local machine with Visual Studio Code and have installed the extensions C/C++ and CMake Tools by Microsoft, and CodeLLDB by Vadim Chugunov.
When I open the folder which contains the CMakeLists.txt file and locate it with the CMake extension, the project is detected and mounted just fine in the CMake tab. The project structure is there, and I can even build it. However, I am not able to access the files through the CMake tab (to edit them and insert breakpoints), as I get this error:
Unable to open 'main.cpp': Unable to read file
'/home/leonardo/Git/MPMc/MPMc/cmake/Git/MPMc/MPMc/MPM/main/main.cpp'
(Error: Unable to resolve non-existing file
'/home/leonardo/Git/MPMc/MPMc/cmake/Git/MPMc/MPMc/MPM/main/main.cpp').
I see it is reasonable that the program cannot read the file, as its address is looped within itself. So what I really wanted was to know how to avoid this behavior so VS Code could see the real address of the files and allow me to access them.
BTW, I am running a Manjaro 18 system and didn't have the same problem with the lab machine, which runs Debian 10.
Could you guys give me any tip as to what could be the solution to this issue? Is this a VS Code issue or a system issue?
Thanks!
I'm trying to use the zlib library in a Visual Studio project I'm writing in C++ but I'm not quite sure how to compile it. I'm running Windows 7 and the source has a makefile so I figured I'd just download Cmake to compile it. Cmake ran perfectly fine with no errors (but 13 warnings) but now I'm left with what can be seen in the image below. What is my next step to compile the code? I figured Cmake would compile it since I had to specify Visual Studio when running Cmake. When trying to open the project files (which is what Cmake yielded) and attempting to compile the source that way, I get a weird access denied error. So yeah, have I gone about this process wrong?
Here's what I see after running Cmake
If I recall correctly, zlib does have the solution file included. It's in
contrib\vstudio\vc14
Try again compiling with that.
CMake is a high-level build manager, it produces a low-level build process files.
You choose to use Microsoft Visual, so it output MSVC project files (.vcproject and .sln). Next step is to open those files with Visual as you did.
So yeah, have I gone about this process wrong?
No you haven't. That weird access denied error must be investigated though.
I am running a sample code of opencv (ocl sample for people detection) in visual studio. When I run the code from this IDE (Ctrl+F5), I get the desired result.
But, When I copy the .exe generated by building the code and run it in another system, I get the following error:
(In another system, I have also copied the required dll to the location where .exe is located)
OpenCV Error:Unknown error code -6 <
OpenCL function is not available: [clGet PlatformIDs]>
The settings of visual studio for the project are:
The configuration type is :Application .exe
Runtime Library: Multi-threaded Debug Dll(/MDd)
A similar question has been posted already but unanswered. It will be of great if anybody has some solutions.
Thank You!!
[edit] Sorry, I out thought myself. I was using a .bat file to set environment variables that wasn't set up properly. When I went to a straight VS2005 command prompt, the configure ran fine. Sorry for the noise.[/edit]
I'm trying to compile qt-everywhere-opensource for embedded. I'm using MSVC2005. However, I guess I am confused on the process. I am getting compiler errors during the configure step. I thought the configure step was just trying to generate the needed makefiles, so I'm not sure what it is trying to compile.
I expected to modify the mkspec, but I'm not sure if during configure I should point to windows headers or sdk headers. I know during the build phase I should point to sdk headers, but I'm not getting that far.
I can change the errors by modifying INCPATH, there's also a QMAKE_INCDIR that seems to have an effect. It occurred to me that since I pulled the source, maybe configure needs to build the compiler tools, in which case I should point to MSVC headers. I also tried downloading the SDK and adding the path to it's bin folder to my path ahead of the -everywhere- source, but that didn't fix the problem and I don't want to jack up my system too much testing things.
Hope someone out there can help!
When you install Qt from source under Win32, you must:
Extend the PATH variable to include $(QTDIR)\bin, where $(QTDIR) is the directory where you installed Qt.
Open a Visual Studio command prompt in $(QTDIR); a plain old Windows command prompt won't do (unless you run vcvars.bat to load Visual Studio's environment variables; but opening a Visual Studio command prompt directly is better).
At this point, configure should run properly, after which you can run nmake.
I suggest that you clear your previous installation attempts from your system before you try these steps.
I am developing a C++ application in Eclipse under Ubuntu Linux 10.10. When I launch the application that I develop in debug mode then Eclipse correctly switches to the debug perspective, but it tries to open a file (?) called ".settings", which does not exist in my project directory (but there is indeed a directory with that name there). I can see that Eclipse supends the running thread at the right source code location (based on the stack trace), but that source file is not opened, nor does the "debug step" move the current instruction pointer to the next statement.
It basically seems to be the same error as here: http://dev.eclipse.org/newslists/news.eclipse.tools.cdt/msg08774.html -- unfortunately the solution there is to update Eclipse to 3.1.5, but I am using version 3.5.2 already, so that does not do the trick for me.
Any suggestions?
Thanks in advance, Matthias
Try to open all projects that are on the source file's path. I've experienced something similar with Java and a hierarchical project and that did solve my problem.