Thanks for the information.
So, I tried and had only limited luck while compiling. The main problem is that cmake does not provide automatically the right parameters to the compiler so that it can finds the standard c++ libraries.
in practice. By default, i.e. by running “cmake -DEASDIF_BUILD_MEX:BOOL=on” or “cmake -GXcode -DEASDIF_BUILD_MEX:BOOL=on”, I get the following problems:
1/ during the cmake command:
“-- Looking for C++ include sstream
– Looking for C++ include sstream - not found
– Looking for C++ include strstream
– Looking for C++ include strstream - not found”
2/ then with “make” or “make mex”:
“[ 0%] Building CXX object easdif/CMakeFiles/Easdif_static_pic.dir/sdifentity.cpp.o
warning: include path for stdlibc++ headers not found; pass ‘-std=libc++’ on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found]
/Volumes/Data2/SDIF/EASDIF_SDIF/easdif/sdifentity.cpp:271:10: fatal error: ‘iostream’ file not found
1 warning and 1 error generated.
make: *** [easdif/CMakeFiles/Easdif_static_pic.dir/sdifentity.cpp.o] Error 1
make: *** [easdif/CMakeFiles/Easdif_static_pic.dir/all] Error 2
make: *** [matlab/CMakeFiles/mex.dir/rule] Error 2”
I got similar errors while compiling from xcode
I tried many options, and went a little bit further and could compile in xcode with the following cmake command:
“rm CMakeCache.txt; cmake -GXcode -DEASDIF_BUILD_MEX:BOOL=on -DUSE_LLVM_STD=1 .”
(since it forces the use of the c++ standard libraries in SET_COMPILER_FLAGS.cmake)
But the “mex” target in the xcode project still does not work. And from the command line (i.e. with “make” or “make mex”) I still get the same errors. BTW: why is it that the command line does not call the xcode project and use a different compilation strategy?