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: * Settings -> Compiler and debugger. 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
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |