CUVILib version 0.3 has been released with a nice set of some core Image Processing and Computer Vision algorithms acclerated on GPUs using NVIDIA CUDA. For those who are not familiar with CUDA or GPU Programming, I would suggest you head on right to NVIDIA CUDA Page. The rest may continue.
So here’s what you will need to use CUVILib to accelerate your applications:
- CUVILib 32/64bit (Click on the link to download the latest version)
- CUDA Runtime version 3.0 (3.1 is recommended but 3.0 will also work)
- NVPP (NVIDIA Performance Primitives) (Click on the link to download the latest version)
- Visual Studio 2005/2008
Step 1: Setting up Environment Variables
Check through the following list and make sure you do not have any of these environment variables missing from your Visual Studio paths.
How to set environment variables in Visual Studio:
Simply go to Tools –> Options –> Projects and Solutions –> VC++ Directories
Now select your Platform from the dropdown menu (Win32 or x64) and then check whether you have the following paths added:
1) %CUDA_INSTALL_DIRECTORY%bin (or bin64 for x64 platform)
1) %CUDA_INSTALL_DIRECTORY%lib (or lib64 for x64 platform)
Step 2: Specifying Additional Dependencies
Go to Project –> Project Properties –> Linker –> Input –> Additional Dependencies
Here’s a screenshot for reference:
Now enter the following Additional Dependencies library files:
1) cutil32.lib (For Configuration=Debug: cutil32D.lib)
3) FreeImage.lib (Optional. Add it if you plan to use the FreeImage library for Image I/O)
5) cuvi32.lib For Configuration=Debug: cuvi32D.lib)
1) cutil64.lib (For Configuration=Debug: cutil64D.lib)
3) FreeImage64.lib (Optional. Add it if you plan to use the FreeImage library for Image I/O)
5) cuvi64.lib (For Configuration=Debug: cuvi64D.lib)
That’s it! You are all ready to go. Now you may use CUVILib with NVPP or as a separate library.
Let me know if you are facing any issues with setting up the project configuration. You can also post your issues on CUVILib forums that would guarantee a prompt reply from one of our dev team member.