4 ms·
The main roadblock is the disgusting combinatoric explosion of compiler versions and debug/release single/multi versions. The "answer" seems to be to download
by eropple 13y ago
The main roadblock is the disgusting combinatoric explosion of compiler versions and debug/release single/multi versions.
The "answer" seems to be to download as source and plug vcxproj dependencies right into your solution. Which, coupled with Windows's problems with static libraries (I use nothing else on OS X - static library right out of Homebrew), is hilarious.
- MaulingMonkey 13y agoSometimes that's the answer. But just yesterday this set of library vcxproj s ended up being generated by CMake... with one supported platform each and absolute paths in them. Not worth even checking into the depot, nevermind including in your .sln, not that the first person to take a crack at it didn't try checking them in and adding them to the sln... It's not even that great a library from what I can tell.
- eropple 13y agoYeah - CMake adds more problems than it solves, IMO. I keep an XCode project and a VS solution and just deal with it.