edit: fixed --with-libraries arg to bootstrap, thanks @sansumbrella
After a bit of elbow grease, all the changes necessary have been made for libc++ support in cinder, and I'm also happy to say that I finally figured out a decent way to build the required boost binaries for this. It's all been merged into the dev branch (thanks, Andrew!) and I'll quickly go over the process here, for anyone else wanting to experiment with the tools of new on OS X.
First, in order to utilize libc++ / C++11 in your cinder app, you first have to make some changes to the project build settings (of both cinder.xcodeproj and your app project file), since it requires minimum sdk versions above those cinder is currently targeting. You must:
Set the Deployment Target:
(OS X) 10.7
Enable C++11 / libc++. Under Apple LLVM Compiler 4.1 - Language:
set 'C++ Language Dialect' to 'C++11'
set C++ Standard Library' to 'libc++
To build the boost binaries, first add the following to your user-config.jam (located in cinder/boost/tools/build/v2):
Note: the path needed by -isysroot may be different in your configuration. To find out the correct path, you can build an iOS app (best to first enable libc++ / C++) in Xcode and look at the build log for any compiled .cpp file. Within the details you will find the actual command used, which contains an '-isysroot /path/to/iphone/sdk..'.
Then run the usual bootstrap so you don't build the entire library (unless you want to..):
Thanks for this. Worked like a charm. I should note I could only get this process to work with boost 1.51, but I did not have the same issue you had with bootstrap (ie, -with-libraries worked fine for me).
Side note: I had some architecture conflicts, probably because I greedily chose 64-bit at some point. My fault, I knew full well that Cinder is only 32-bit compatible for now. In any case, what is the current correct architecture choice in the build settings? I believe it is i386 initially, but once I select 32-bit Intel or Standard (32/64-bit Intel), the i386 option disappears.