Integration with XCODE? Anyone created a CUDA template project?

[jmazo]

Hi there

my 2 cents

the plugin and the template seem to work fine with 2.3a in Xcode 3.1.2 in leopard.

and the path has not changed, its been in /usr/local/cuda as long as I can remeber

it was the examples (SDK?) that changed from /Developer/CUDA to /Developer/GPU Computing

One of the problems that I noticed in moving from the 2.2 to 2.3 drivers and sdk is that the CUDA plugin seemed to continue to try to access the 2.2 version of nvcc, and downstream compilers, etc (the install location changed from 2.2 to 2.3, I think). That might need to be looked at. Better yet, it might be nice to be able to explicitly set the path to the bin folder… maybe. Just a thought.

Paul

[PTThompson]

I should mention that with the project template, if you want to write your program in C, it works just fine, but ONLY if you make sure to leave at least one .cpp file in the project with the ‘target’ box checked. I’m not sure why, but if there isn’t a cpp file, xcode balks and you get a linking error. There doesn’t have to be anything in this .cpp file, and your main can be a main.c. You just have to have it there.

Paul

[jmgiorgi]

A Noob question: How (and Where) do you set the include path for nvcc?
Keep up the good work! Cheers,
JM

[PTThompson]

A Noob question: How (and Where) do you set the include path for nvpp?

Keep up the good work! Cheers,

JM

I’m not clear on what you’re asking. Do you mean the path for nvcc to use to search for libraries, etc, or the path to nvcc itself?

If you mean the path for nvcc to use to search for libraries… like if you have additional non-standard libraries that you want to include in your project, and you don’t store them in the project folder itself, then you might have to pass a path flag to nvcc… something like a “-P /blah/moreblah/thatfolderinblah/stuff/” or something.

If you mean the path to nvcc itself, then you can use a symbolic link file (like an alias, but unix style) in your /usr/local/bin/ folder to point to the actual location of nvcc. Do some googling and you should be able to figure out how to do that (I forget off the top of my head).

Or did I miss the question completely?

Paul

[MacFan]

Would it be possible for someone to summarize the precise current state of affairs here. Do we have working Xcode solution for

2.3a under Leopard
3.0 under Snow Leopard

and in either case is there a concise summary of the steps needed?

[Blair_Chen]

Would it be possible for someone to summarize the precise current state of affairs here. Do we have working Xcode solution for

2.3a under Leopard

3.0 under Snow Leopard

and in either case is there a concise summary of the steps needed?

I just upgrade CUDA from 2.3a to 3.0 beta1 and XCode from 3.2 to 3.2.1 for my Snow Leopard.

The xcode plugin in this thread seems not to work for my configuration first, but I make one from the source.

Finally it works for me. So I think 2.3a and 3.0 are ok under Snow Leopard (32) and so far as XCode solutions.

Sincerely,

Blair

[coding_md]

I just upgrade CUDA from 2.3a to 3.0 beta1 and XCode from 3.2 to 3.2.1 for my Snow Leopard.

The xcode plugin in this thread seems not to work for my configuration first, but I make one from the source.

Finally it works for me. So I think 2.3a and 3.0 are ok under Snow Leopard (32) and so far as XCode solutions.

Sincerely,

Blair

Hi Blair,

I’m new to CUDA and was wondering how were you able to make one from the source.

I am using Xcode 3.2 64-bit, CUDA driver 2.3.1a, CUDA SDK 2.3a, CUDA toolkit 2.3a under Snow Leopard.

Has anyone been able to get an updated plugin for Snow Leopard?

Thanks,

Mo

[coding_md]

Sorry, double post.

[bamdadhosseini]

Ok, so i have downloaded the two files and put them in the folders said below. Now as i enter Xcode i can choose the CUDA template alright and i can also compile the “hello world” program while including <omp.h>. the only problem is that in the information section of my project, the variables and configurations are different. i dont have a section called “Custom settings for NVCC” or sth like it. does this mean that i have a problem? i have not yet checked any actual CUDA code with this.

Ok, so I managed to get CUDA working in Xcode with OpenMP. It took me a while, so I figure I might as well post all the details to save others the trouble.

The first problem is that the current version of Xcode uses GCC 4.0.1 by default, which does not support OpenMP. Inside an Xcode project, we can specify which version of gcc to use, but NVCC doesn’t care about our choice, and goes ahead and uses the system default anyway. So you have two options: You can either install the latest version of gcc, as I did, or you can change the system default. Changing the system default to GCC 4.2 (which is included in the latest release of xcode) has the advantage that it is an Apple build, and therefore has all the extra Mac OS X stuff built in. Installing a new release has the advantage that you won’t have to change the system default.

To change the system default, navigate to ‘/usr/bin/’ and type:

‘sudo rm gcc’

then:

‘sudo ln -s /opt/local/bin/gcc-4.2 gcc’

This will delete the existing symbolic link, which points to gcc-4.0, and replace it with one that points to gcc-4.2. Your system default is now changed.

Going the other route, you can download and install macports, and the very nice gui front end, ‘Porticus’, and have it download and install the latest version of GCC (in my case, it was 4.4)'. The catch is that it will download the SOURCE for gcc, and then proceed (very VERY slowly) to compile it. It took about 3-4 hours on my second generation MacBook Pro, so be forewarned. Once the new version of GCC is installed (let’s assume that it put it in ‘/opt/local/bin’, as it did for me), navigate to the install directory and type:

‘sudo ln -s /opt/local/bin/gcc-mp-4.4 gcc’

to make the symbolic link you need (this assumes that you want the gcc-mp-4.4 binary to be the default for this installation, as I did).

Now, the next step is to enable Xcode to recognize .cu files, and let it know what the heck to do with them. For that, you need a slightly modified version of Llamatron’s awesome plugin, which I’m attaching below. The change is that I’ve added a project build option to allow you to pass options to the NVCC compiler directly. So download the NVCuda.pbplugin.zip file, decompress it (should happen automatically), and place it in your ‘/Users//Library/Application Support/Developer/Shared/Xcode/Plug-ins/’ directory. If the plug-ins folders doesn’t exist, just create it.

Next, download the CUDA project template file, ‘CUDA Projects.zip’, and decompress it. This folder goes (for Xcode 3.1) in ‘/User//Library/Application Support/Developer/Shared/Xcode/Project Templates/’. Again, if Project Templates doesn’t exist, just create it. Be sure that when you move the folder, that you move the ‘CUDA Projects’ folder, which contains ‘CUDA C/C++ App’, and not just the sub folder itself. If you forget the ‘CUDA Projects’ folder, Xcode probably won’t recognize the project.

Now it’s time to start Xcode. Once Xcode is up, choose ‘New Project…’ from the File menu, and you should see a ‘CUDA Projects’ category under User Templates. Choose the only option (CUDA C:C++ App), and hit ok.

Now, to test it out, lets add ‘include <omp.h>’ to the .cu file. If you simply changed the system default compiler to GCC 4.2, then at this point you should be able to compile with no errors. If we forgot something, then you’ll probably get an error saying that omp.h doesn’t exist. In that case, you’re on your own to figure it out. :P sorry. Now, if you installed a new version of GCC, such as 4.4, as I did, then there’s one last step we have to take before we can compile. In the project window, under Groups & Files, on the left, click on your project file, and then the info icon. Go to the Build tab, and scroll all the way to the bottom. You should see a setting labeled, “Custom Options for NVCC”. If you don’t see it, then I screwed up somehow, and again, you’re on your own. Assuming you see it though, this is where we tell NVCC where to look for the new gcc compiler (which knows how to handle OpenMP). The command to insert is ‘-ccbin=/opt/local/bin’ (assuming that you installed the new gcc to /opt/local/bin, of course.) The -ccbin option is the same thing as ‘–compiler-bin-dir’, and just tells it where to look. So NOW, finally, you should be able to Build & Go with no errors. If it doesn’t work, then, yes, you’re on your own. But if I did screw this stuff up somehow, and someone figures it out, by all means let me know and I’ll try to fix it.

Enjoy, and good luck!

Paul

[attachment=12756:CUDA_Projects.zip]

[attachment=12757:NVCuda.pbplugin.zip]

[PTThompson]

Ok, so i have downloaded the two files and put them in the folders said below. Now as i enter Xcode i can choose the CUDA template alright and i can also compile the “hello world” program while including <omp.h>. the only problem is that in the information section of my project, the variables and configurations are different. i dont have a section called “Custom settings for NVCC” or sth like it. does this mean that i have a problem? i have not yet checked any actual CUDA code with this.

Sorry, haven’t been checking the forums lately. I actually haven’t used cuda at all in months, due to classes getting in the way (in final semester atm). If I recall correctly, the cuda specific settings would only show up if you had a particular file type in the project. It may have been a .c, or a .cu, or .cpp. If you fool around with different combinations of dummy files, in addition to the normal hello world files, it might show up properly. However, since we’re now two or three cuda releases past the one that the plugin was made for, and at least two past the one I made the templates for, it’s probably rather likely that the stuff is simply broken.

What we REALLY need is either someone from Apple, or someone else who knows the Xcode plugin system REALLY well, to start maintaining the plugin and templates. Honestly, I’m not sure why there isn’t already some official plug in. The only thing I can guess is that Apple refuses to make it since they want to push OpenCL, and NVIDIA doesn’t have access to the guts of Xcode to make it less than a major pain in the butt to do.

Maybe we should all start emailing apple though? I’d personally really like to see better support for scientific programming in xcode, including fortran support, cuda support, etc. There’s really no good reason that mac using scientists should be stuck with technology from 30 years ago when we want to write programs. Give us a little love!

Paul

PS another possibility might be that you have the wrong version of the plugin and templates. I modified the original plugin and that is how it came to have the line for custom nvcc tags, or whatever it was. So also sift back through the posts and see if you’ve got the version I posted.

[vivekv80]

How to fix this ?? (Snow Leopard with Xcode 3.2.1, CUDA 2.3)

I just want to run Xcode without the NV plugin for other projects.

I don’t have any plugin directory in /Library/Application Support/Developer/Shared/Xcode so why is this crashing with NVCudaOutputParser flag?

I can compile CUDA projects from terminal as I have the correct path set up.

Unfortunately the plugin is not working anymore with Snow Leopard and XCode 3.2. XCode crashes when launching:

Exception Type:

EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:

objc[3530]: garbage collection is ON

objc[3530]: layout_bitmap_or: layout bitmap too short: NVCudaOutputParser

NSCFDictionary

Any ideas? Thanks.

[PTThompson]

How to fix this ?? (Snow Leopard with Xcode 3.2.1, CUDA 2.3)

I just want to run Xcode without the NV plugin for other projects.

I don’t have any plugin directory in /Library/Application Support/Developer/Shared/Xcode so why is this crashing with NVCudaOutputParser flag?

I can compile CUDA projects from terminal as I have the correct path set up.

Double check both the user specific library folder (in my case it’s /Users/TraxusIV/Library/Application Support/Developer/Shared/Xcode/) as well as the root library folder (/Library/Application Support/Developer/Shared/Xcode). Sometimes the plugin may be in one, or both locations. After making sure that the stuff is gone from there, I’d reinstall Xcode. You can download the latests version from Apple’s ADCM site if you have access, or perhaps from the downloads section of the main site… lemme see… Hmmm, go here: http://developer.apple.com/mac/ though you may have to register (can be free) to download it. Otherwise, xcode is included on every OS X install disk, so just grab the latest version you have and install. Should be in the Optional Installs folder or something.

That’s my best recommendation, unfortunately. Sorry I can’t be any more help. :(

Paul

[vivekv80]

Thanks Paul. That worked :)
Deleted the NVCUDA plugin from ~/Library/Application Support/Developer/Shared/Xcode/

[thewoz]

I have Snow Leopard, version 10.6.2 and Developer Version 3.2.1, 64 bits on a Mac Mini.

I have put the NVCuda.pbplugin BOTH in

/Library/Application Support/Developer/Shared/Xcode/Plug-ins
and
$HOME/Library/Application Support/Developer/Shared/Xcode/Plug-ins

without any effects. It does not work!

What should I do?

Should I recompile the plugin? And if, from which sources and how?

Thank you!

[ant-fx]

I have Snow Leopard, version 10.6.2 and Developer Version 3.2.1, 64 bits on a Mac Mini.

I have put the NVCuda.pbplugin BOTH in

/Library/Application Support/Developer/Shared/Xcode/Plug-ins

and

$HOME/Library/Application Support/Developer/Shared/Xcode/Plug-ins

without any effects. It does not work!

What should I do?

Should I recompile the plugin? And if, from which sources and how?

Thank you!

You must download and copy “CUDA Projects” folder to “$HOME/Library/Application Support/Developer/Shared/Xcode/Project Templates”.

But it not works too. At first - “warning: no rule to process file…” to .cu-files during translation.

It’s interesting, when NVIDIA developers will say something about SLeo+Xcode3.2.1+CUDA3? And it will be a great deal to make Xcode 3.2.1 templates for Cocoa and Carbon projects with CUDA (Current state of integration is natural nightmare)

[thewoz]

You must download and copy “CUDA Projects” folder to “$HOME/Library/Application Support/Developer/Shared/Xcode/Project Templates”.

But it not works too. At first - “warning: no rule to process file…” to .cu-files during translation.

It’s interesting, when NVIDIA developers will say something about SLeo+Xcode3.2.1+CUDA3? And it will be a great deal to make Xcode 3.2.1 templates for Cocoa and Carbon projects with CUDA (Current state of integration is natural nightmare)

I have rebuild the plugin for osx 10.6 and now work for me!
NVCuda.pbplugin.zip (11.2 KB)

[ant-fx]

I have rebuild the plugin for osx 10.6 and now work for me!

Lucky man! :-)

Still “no rules…” When I try to set rule manually in Target settings, nvcc don’t want do it.

Have you installed previous CUDA version, or install 3.0 “clear”?

[thewoz]

Lucky man! :-)

Still “no rules…” When I try to set rule manually in Target settings, nvcc don’t want do it.

Have you installed previous CUDA version, or install 3.0 “clear”?

I have Os X 10.6.3 xcode 3.2.1 and CUDA 3.0 all install for “clear”.

I take the src of the plugging and I rebuild it without problems.

dont’t ask me why, but on a mac mini with CUDA 3.0 and SL, xcode refuse to build it.

I speak only about the nvCuda.pbplugin I never try yet to compile with xcode a .cu file

[Dreampursue]

I have rebuild the plugin for osx 10.6 and now work for me!

I have Os X 10.6.3 xcode 3.2.2 and CUDA 3.0.

I have downloaded the lasted plugin. And I do it as you say. But it also doesn’t work…

What’s the problem?

Thank you!

[thewoz]

I have Os X 10.6.3 xcode 3.2.2 and CUDA 3.0.

I have downloaded the lasted plugin. And I do it as you say. But it also doesn’t work…

What’s the problem?

Thank you!

Hi I never test the plugin with xcode 3.2.2 I have the old 3.2.1 but I don’t believe that this is the problems.

I have put the rebuild plugin in this directory

/Users/theWoz/Library/Application Support/Developer/Shared/Xcode/Plug-ins/NVCuda.pbplugin

this work for me…

I sugest you to try to download the source code of the plugin and rebuild it on your machine…

I not the creator of the plugin and I’m not able to touch the code of it…

I hope that can help you.