Compilation Error

Oct 16, 2014 at 7:20 PM
Edited Oct 16, 2014 at 11:02 PM
Hello!
I have seen many similar themes, but not found a solution.

Details of my problem:
OS - Windows 8.1 64 bits.
DevTool - VS 2012
CUDA SDK - 6.5 for Win 8.1 64 bit
CUDAfy - V1.27 Installer
I have an old video card - GTS 250 and its computational compatibility 1.1.
I use overloaded Cudafy() function for Module Compilation but it does not work.

I have the following code:
            CudafyModule km = CudafyTranslator.Cudafy(ePlatform.Auto,
                gpu.GetArchitecture(),
                Property.Capability,
                true,
                typeof(KernelContainer));
and get the Error "can't find the specified file"
If i use the CudafyOld() - get the Compilation Error.

In nvcc.profile i have follow content:
TOP              = $(_HERE_)/..

NVVMIR_LIBRARY_DIR = $(TOP)/nvvm/libdevice

PATH            += $(TOP)/open64/bin;C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin;$(TOP)/nvvm/bin;$(_HERE_);$(TOP)/lib;

INCLUDES        +=  "-I$(TOP)/include" "-IC:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include" $(_SPACE_)

LIBRARIES        =+ $(_SPACE_) "/LIBPATH:$(TOP)/lib/$(_WIN_PLATFORM_)"

CUDAFE_FLAGS    +=
OPENCC_FLAGS    +=
PTXAS_FLAGS     +=
What did I do wrong? Did install wrong version sdk or cudafy?
Oct 17, 2014 at 2:43 AM
Edited Oct 17, 2014 at 2:44 AM
Mmm... i add variable in systems environment variable with path to the cl.exe
PATH = C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\amd64
and now i have new error - Unable to load DLL "cudart32_55" in this code line
GPGPUProperties Property = gpu.GetDeviceProperties(true);
And even after the removal of PATH variable the error still rise!
Coordinator
Oct 17, 2014 at 7:43 AM
Edited Oct 17, 2014 at 7:43 AM
You have CUDA 6.5 installed and it is not finding CUDA 6.0 or 5.5 which is needed for cudart from CUDAfy V1.27. If you build CUDAfy yourself this will be resolved.
Otherwise you can pass false to GetDeviceProperties and it will not use cudart.
Oct 17, 2014 at 9:24 PM
Yes, it solved the problem!
Thank you!