One thing to try is adding another compiler for running in CUDA's device-emulation mode.
CODE BLOCKS NO COMPILER UPDATE
Good luck! I will update here if I find any further improvements to the system. Now go forth and test thy new-fandangled compiler and report back to me if you find yourself in more trouble than you began (I hope not). Alternatively you could add it to the global compiler settings. If you're setting up a project yourself, just add cutil to the Link libraries box in your project's build settings.
Note that many of the SDK samples need to be linked against the cutil library. Just extract it to your SDK directory and open projects.workspace. If you want to try compiling the SDK sample projects, this may be of use, which contains Code::Blocks project files I created for a few of the samples. Woot, that's it! Now you can try making a project that uses the NVCC compiler. Select 'Instantiated from' info and replace the regular expression (regexp) with: (+)(+)\)?:(.*).Replace the Command line macro with this: $compiler -compiler-options "$options" $includes -c $file -o $object.Within the Commands tab, select Compile single file to object file.You will be prompted with a very frightening warning about goblins attacking your home if you dare continue.Take a deep breath, then click Advanced options.Scroll right (i.e., not left) through the tabs until you can see the Other settings tab.Select your new NVIDIA NVCC CUDA Compiler from the list at the top.Here's a step-by-step guide, because I'm feeling typeative: But those nasty issues I discussed in the first post remain to be dealt with. In the Build tab, tick Compile file and Link file.cu file(s) in the file tree on the left and go to Properties. cu files that need to be compiled, not for those acting as headers that are included by another file! cu file, you'll have to do something slightly annoying, because I haven't found a way to automate it. Project -> Project tree -> Edit file types & categories.Before we get into the really fun stuff (as described in my original blog post), we'll do a couple of easy things to make life more convenient. Add /your_location/NVIDIA_CUDA_SDK2/common/lib/linux (modify for your OS) to the Linker box.Add /your_location/NVIDIA_CUDA_SDK2/li b to the Linker box.Under the Search directories tab, add /your_location/NVIDIA_CUDA_SDK2/common/inc to the Compiler box (so that headers like cutil.h will be found).
Debugger: cuda-gdb? (I haven't actually tried it yet).Enter nvcc's installation directory (e.g., /opt/local/cuda).Do exactly what you're told, and go to the Toolchain executables tab.Something like "NVIDIA NVCC CUDA Compiler", but perhaps with less shouting. At the top under Selected compiler, make sure "GNU GCC Compiler" is selected, and click the Copy button.Here I'll outline the procedure for setting up the nvcc compiler in Code::Blocks from scratch.įirst we create a new compiler within Code::Blocks. While my first post highlighted the key sticking-points I faced when I first tried to use the nvcc compiler within the Code::Blocks IDE, it was probably jumping the gun a bit.
0 kommentar(er)
