[SDL] Non-API changes I'd like to see in SDL 2.0

Ryan C. Gordon icculus at icculus.org
Tue Mar 11 19:54:00 PDT 2008


> All of these factors convinced me not to use CMake for my own projects, 
> so I never bothered investigating it in more detail.  When compiling 
> third party libraries, factor 1 is enough to annoy me.

Was autoconf unacceptable, too? Because it's arguably the same thing as 
CMake, minus a scripting language that may or may not suck more than 
CMake's scripting language, and it only generates for one type of build 
system.

As much as autoconf annoys me, once you scale to something as large as 
SDL (which isn't THAT large, all things considered) and support a few 
different flavors of Unix, it helps way more than it hurts.

Also, I personally try to find the fastest route to a bash shell on 
_any_ platform, but I can't tell you the number of emails I've gotten on 
other projects complaining that there isn't a [visual studio 6/7/8/9/10 
| XCode | Dev-Cpp | Watcom | Code::Blocks | whatever] project file. Even 
if I wasn't an elitist Unix jerk, I wouldn't want to spend time 
maintaining all of that, and in those cases, something like CMake could 
be really useful.

(There really is a lot that could improve about CMake, though...but "can 
generate project files for Developer IDEs you don't personally care 
about" is a REALLY compelling feature).

--ryan.



More information about the SDL mailing list