Tweet
We've decided that we'd like to be a bit more systematic about supporting people trying to build on Windows, and clearer about what is and isn't supported. Most of the current devteam use linux (or Mac, which is unix-y) by default for hacking, building and playing - although we can cross-compile for Windows, and even test under WINE, it's not quite the same. The vague consensus among us is, perhaps not surprisingly, to standardise building for Windows using MinGW, MSYS and msysgit. This is a command-line-driven unix-like environment, hence the easiest for us to master and support. It's also how fizzix, who is essentially the one Windows-based member of the devteam, builds.
There are other options though. Blubaron uses Visual Studio, and so do some others. There's also DevC++ and Eclipse, which are both free.
Supporting GUIs is a much more difficult task than supporting a CLI approach, because it requires very careful descriptions (or screenshots) of exactly what to click, and different versions have subtle UI differences which will ruin careful guidance at a stroke. We would probably only be able to support one of these IDEs, and probably only with significant help from a new team member.
I guess what I'm asking is, how many people give a stuff about this? Those who have found a way of building their own versions in Windows would probably prefer to stick to what works for them. Is there anyone who would like help to build on Windows but can't, and would be prepared to use a CLI to do it? Or is there anyone who would like to evangelise about their preferred free Windows IDE to the extent of helping the devteam to help others?
There are other options though. Blubaron uses Visual Studio, and so do some others. There's also DevC++ and Eclipse, which are both free.
Supporting GUIs is a much more difficult task than supporting a CLI approach, because it requires very careful descriptions (or screenshots) of exactly what to click, and different versions have subtle UI differences which will ruin careful guidance at a stroke. We would probably only be able to support one of these IDEs, and probably only with significant help from a new team member.
I guess what I'm asking is, how many people give a stuff about this? Those who have found a way of building their own versions in Windows would probably prefer to stick to what works for them. Is there anyone who would like help to build on Windows but can't, and would be prepared to use a CLI to do it? Or is there anyone who would like to evangelise about their preferred free Windows IDE to the extent of helping the devteam to help others?
Comment