tksharpless

Two more lines in cmakelists.txt contain gcc-isms that give msvcc commandline errors: 36 set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -Wall -Wsign-compare") 76 set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Werror") in msvcc -W expects a numeric argument, but...

Hi Albert, Although I was able to get legal VC projects by adding one line to cmakelists.txt and removing two others, it appears to me that it will be impossible...

Hi Albert, The issue that concerns me most is generating calibrations for the kinds of rigs we now use to capture stereo still panoramas. A full "bubble camera" array is...

Hi Albert On second thoughts, and more careful reading of the code, I can see that there is nothing about your camera model that needs fixing. Good job. I would...

Having better luck compiling with VC 15 (Visual Studio 2017). But found what looks like a real source code issue: the code uses 'filesystem::' and 'boost::filesystem::' as if they were...

Yeah, Ifound that > #ifdef WIN32 #include #else #define BOOST_FILESYSTEM_NO_DEPRECATED #include #endif But this will not work because the code has "boost::filesystem::" in many places. The answer is obviously to...

That leaves just one compile error in calibration lib. The definitinion of _Associated_state in VC's future.h assumes the target class is default-constructible (this is marked with a ToDo) and sad...

BTW the string conversion problem comes from the fact that boost::filesystem::path is wchar on Windows but char on nixoids.

I have been able to compile the calibration library for Windows with VC 2017 with reasonably few code changes. The most significant is eliminating the multithreaded driver function. I plan...

It appears that I will be able to build your multithreaded calibration program as-designed. The issue with future that was worrying me is trivial to get around -- just define...