helios has a strong point about debugging, and I agree.
However, dependence on another project is yet another thing to maintain. This may cause unforeseen problems:
1. Do all your team mates know SDL? (not all programmers do: for example, myself).
2. What happens when SDL changes version, who is responsible for updating?
3. How much larger does your executable get? How much of the actual SDL functionality are you using?
4. 3 x 1000 lines of code does not seem so horrible. One should be able to read and understand that much code in under a week. How long does it take to download, install and learn SDL?
In other words, I don't see immediately which is better: a tested external solution or an in-house "quick-and-dirty" solution to a relatively small and specific problem. I think it's a close call, and it may actually depend on what your colleagues think.
|And apparently nobody wants to go through the hassle of compiling SDL|
My personal experience with compiling large "established" projects has been extremely painful: I tried wxWidgets and FOX GUI on separate occasions. The amount of time I spent reading their documentation, going through forums, setting up configuration files and fighting with updates of their system breaking my code was, in my opinion, larger than the amount of time I needed to do everything myself.
I ended up scrapping my GUI and redoing everything within the web browser for 1000 times better result with much less code and hassle.