Resolve/C++ on Mac OS X

March 27 2010 08:19 AM

I use TextWrangler on Mac OS X to do all my Resolve/C++ coding.

Because Resolve/C++ isn’t a standard to most of the world, until now I had to deal with only having standard C++ syntax highlighting.

But, I’ve put together a language module for TextWrangler and BBEdit to highlight Resolve/C++’s key words. These keywords came straight from the list used by XEmacs (see /class/sce/rcpp/setups/rcpp-mode.el).

I’m making this language module freely available. All I ask is that if there are any changes, they should be made available for all.

To use, simply copy the file resolve.plist to ~/Library/Application Support/TextWrangler/Language Modules/ and restart TextWrangler.

Update: Since I have been receiving quite a few emails asking the same question, I’ll answer it here: I did NOT set up Resolve/C++ to be able to compile on a mac. I had originally investigated getting the resolve libraries onto a mac, but I never really ended up with enough time to give it justice. The solution that I found worked best for me was to use TextWrangler with the Resolve/C++ plugin I made to edit over SSH to the student servers and test them from there over SSH. When you open TextWrangler, go to the File menu and select Open From FTP/SFTP Server. SFTP is essentially the same as SCP (file transfer over SSH).

You can set up private key authentication with the server to streamline things a bit more if you want.

Aside from that, if you really want to compile Resolve/C++ code on Mac OS X natively, all I can really do is point you to the current source code tree for Resolve/C++ and leave you to your own devices for getting it going. If you log into the student server (stdsun, via ssh or a lab terminal), you’ll find the current source tree at /class/sce/rcpp/. The rcpp-make script is in the tools subdirectory. I think it would only be a matter of copying the complete directory tree to a local directory, setting the $RCPP_HOME environment variable (as seen in rcpp-make) to the local directory, and adding the tools directory to your $PATH environment variable. Unfortunately I still do not have the time to really investigate this, nor do I have any particular desire to pursue it any further, but hopefully this can help lead you in the right direction.

If someone happens to take the time to get Resolve/C++ compiling on Mac OS X, I’ll be happy to check it out and post an update with the information.