Changes between Version 11 and Version 12 of GPUApp

Timestamp:

Jul 8, 2010, 3:02:55 PM (14 years ago)

Author:

Nicolas

Comment:

--

GPUApp

@@ -16 +16 @@
 The VS project file, example_app_nvcuda.vcproj, is in "boinc/win_build/".
 Note that NVIDIA Cuda SDK 3.0 or older supports device emulation mode.
-If your machine doesn't have a Cuda-enabled GPU,
+If your machine doesn't have a CUDA-enabled GPU,
 then you should build the sample app in the device emulation mode.
-Do so by setting "Build -> Configuration Manger -> Configuration" to either Emudebug|Emurelease.
+Do so by setting "Build -> Configuration Manger -> Configuration" to either Emudebug or Emurelease.
 It comes to our attention that while compiling the sample app,
 the linker tries to link both the debug and release libraries, and thus causing the following errors:
@@ -27 +27 @@
 ...
 }}}
-One solution to this problem is to set the Hyprid Cuda/C++ Runtime Library to "Multi-Threaded Debug (/MTd)".
+One solution to this problem is to set the Hybrid Cuda/C++ Runtime Library to "Multi-Threaded Debug (/MTd)".
 Do so by right click on the project.
 Set "Properties -> Configuration Properties -> Cuda Build Rule v3.0.14 -> Hybrid CUDA/C++ Options -> Runtime Library"
@@ -81 +81 @@
 is installed at the default location "$(ROOT)/home/USER_NAME/NVIDIA_GPU_Computing_SDK/".
 On my Linux machine, for example, it would be "$(ROOT)/home/tuanle/NVIDIA_GPU_Computing_SDK/".
-Since the absolute path is used in Makefile, you will probably need to edit file "common.mk" before compiling the sample app.
+Since the absolute path is used in Makefile,
+you will probably need to edit file "common.mk" before compiling the sample app.
 Do so by looking for "/home/tuanle/NVIDIA_GPU_Computing_SDK" in file "common.mk"
 and replace this path with an appropriate path on your machine.
 
-What if your machine doesn't have an NVIDIA Cuda-enabled GPU?
-Then, you can compile and run your app in emulation mode.
+If your machine doesn't have an NVIDIA Cuda-enabled GPU,
+you can compile and run your app in emulation mode.
 As far as we know, NVIDIA Cuda SDK 3.1 no longer supports emulation mode.
 Thus, you will need to install an older Cuda SDK version, like version 3.0, on your machine.
@@ -116 +117 @@
 
 The Makefile for Linux is made with the assumption that the ATI Stream OpenCL
-SDK version 2.1 for 32-bit Linux and Boinc are installed in the same parent directory,
+SDK version 2.1 for 32-bit Linux and BOINC are installed in the same parent directory,
 i.e. "ati-stream-sdk-v.2.1-lnx32" directory and "boinc" directory are both installed at "$(ROOT)/home/" directory.
-If you are using the SDK v2.1 for 64-bit Linux, or if Boinc and the OpenCL SDK
+If you are using the SDK v2.1 for 64-bit Linux, or if BOINC and the OpenCL SDK
 are not installed in the same parent directory,
 then Makefile needs to be edited prior to any compilation.
@@ -180 +181 @@
 === NVIDIA Cuda ===
 
-Unlike Windows and Linux, the 'nvcc' cuda compiler for Mac has some trouble compiling .cu files that
-contain both BOINC and Cuda codes.
+Unlike Windows and Linux, the 'nvcc' cuda compiler for Mac
+has some trouble compiling .cu files that contain both BOINC and Cuda code.
 Any attempt to compile such .cu files might result in errors like
 these:
@@ -200 +201 @@
 while the function headers with "extern" prefix are put in .c file and can be called in main function or elsewhere.
 
-What if your machine doesn't have an NVIDIA Cuda-enabled GPU? Then, you can compile and run your app in emulation mode.
+If your machine doesn't have an NVIDIA Cuda-enabled GPU, 
+you can compile and run your app in emulation mode.
 As far as we know, NVIDIA Cuda SDK 3.1 no longer supports emulation mode.
 Thus, you will need to install an older Cuda SDK version, like version 3.0, on your machine.