You don't need to do that. You can perfectly edit the CMakeLists.txt from visual and just build your project normally. Visual Sutdio project will be rebuilt automatically. Tweaking the build is only needed, when you generate the project for the first time.
CMake and Visual Studio don't tend to play well together.
I guess that depend what you called users. I understand your point for developpers. But normal users won't compile openxcom, they just want precompiled binaries.
Most Linux users prefer to compile it themselves, probably because precompiled binaries don't play well with all the different distros and setups out there.
Sorry, I didn't mean to be a PITA, I just wanted to make sure everyone understood what your intention was, so that you'd get meaningful responses.
1. Some IDEs support CMake, either out-of-the-box or by adding a plugin. Perhaps you can let your IDE take care of those changes for you.
2. It's not that hard, and if your IDE supports it, it's even easier. I'd be motivated to learn it if it meant reducing the amount of work I have to do for supporting the people who want to compile my code.
AFAIK there are no such solutions for Visual Studio. And well I'm not completely clueless, if push comes to shove I will dig around the files to tweak and fix something, but more often than not the contributors handling the CMake/Autotools do a much better job than me.
3. It's your project. F*** them 
Seriously, you will always find some resistance, whatver choice you make, and unless you want to support every major tool in existance - which you don't, that being the exact purpose of this poll - you will always have some people unhappy with something. But you can always accept contributions from them, in order to unofficially support their platform of choice. Just drop their build files somewhere in "build/<platform>/*.*" and that's it. Personally I don't like that, because it will eventually mean that those build files will be out of sync with the project, and someone will make a fuss about it. But apart from having a big team and people dedicated to maintaining those build feils, I think that's the only sane way of supporting a lot of platforms.
Raúl
Well I'm one of those people.
I'm primarily a Windows developer (a capital OSS offense!), so I could just maintain a VS project and f*** the rest, but that wouldn't be very nice.
And that's pretty much how it works right now. Most "secondary" build tools like CMake/Autotools scripts are maintained by outside contributors, and I'd love to just leave it all in their capable hands but eventually the code updates faster than the tools and if someone is using them I have to step in myself and keep everything in sync.
It probably doesn't help that I haven't been able to keep up with Linux support, since my distro is currently broken and I only have enough experience to put out a binary that apparently only works on my machine, so whenever there's an issue there I'm pretty much helpless. Maybe someone would be interested in keeping all these things in check for me and make proper binaries and packages and what not?
Poll
