Really the only reason Windows isn’t considered a supported platform for cmake builds is that we haven’t finished it, but there are many avenues there that seem promising. I took an initial stab for CLion / mingw and ran into a bunch of shortcomings with the compiler toolchain there (it is old and incomplete). I believe that CLion folks are planning to support the MSVC toolchain sometime this year. Hai afterwards put some work into generating proper Visual Studio project files, and I think that was working (if not, very close). More recently, Visual Studio 2017 (released yesterday) supports building cmake files directly, so that also seems like something worth trying.
To give some history on how we arrived here: our CMake support began out of necessity for building libcinder on Android, and then linux. At that point, partly due to OS X’s Xcode performing progressively worse with large C++ projects, we unified the system so that CMake could be an option on any platforms. We invested quite a lot of energy into that, including blocks support and CI integration and continue to do so, however cmake on windows could use a community champion.
We’ve agreed that for the time being, the hand-tuned Xcode and Visual Studio project files will remain, until such a point that there is no longer any benefit to maintaining them. At current, the hand-tuned project files are much more sane and easy to operate than those generated by cmake, but there’s nothing stopping users from using cmake generated projects, and hopefully we’ll see some improvements there as more people are adapting to the cmake builds and begin contributing. The best part about cmake is that it is used industry wide, so there really isn’t anything that we’d want to do that some other project hasn’t figured out, the methods just need to be sought out and implemented.
Hope that helps clarify the current situation! Bit by bit, cinder is becoming a full-fledged cross platform library.