Move to c++0x/c++11 instead of boost version of shared_ptr to remove boost dependency

[Sam Preston]

This is the purpose of nikhil's boost_to_cxx0x branch. After some research though it looks like there's no way to get nvcc to compile code that uses c++0x headers or constructs. It might be possible to remove shared_ptr references from nvcc-compiled code, but it would be a major restructuring, so this issue will likely be tabled for a while.

[Sam Preston]

As mentioned, we pretty much have to wait for nvcc to support c++11 constructs before this will work

[Jacob Hinkle]

Hell will freeze over first, I'd imagine. If this was important we could probably switch to OpenCL in the time it takes to wait on nvidia to update something.

[Sam Preston]

(Reply via [e-mail]):

Yeah, 'on hold' or 'wont fix' are equally applicable. We'll have to deal with the boost dependency for now, but I don't think that's too bad -- plenty of projects rely on boost, it's a pretty standard dependency. The other option is to just get rid of the shared_ptrs, but like I said, the boost dependency doesn't bother me too much. The issue was specifically on atlas1&2 where the mpi libraries are installed from source and the standard boost libraries come with a boost_mpi module which wants to reinstall the default mpi packages, but I think we can set up a workaround pretty easily.

On Thu, Jan 24, 2013 at 9:33 PM, Jacob Hinkle [e-mail] wrote:

[Jacob Hinkle]

now that boost is sequestered, i've started a c++11 branch to try and remove boost entirely

[Jacob Hinkle]

The main thing holding this back so far is that I'm not sure how to set the -std=c++11 flag for gcc/clang but NOT nvcc. Also there were some problems w/ some of the ITK headers under C++11