[SDL] Correct way of including SDL?

L-28C kixdemp at gmail.com
Tue Sep 4 06:12:05 PDT 2007


Bill Kendrick wrote:
> No.  You #include "SDL.h".  And if 'sdl-config' is unavailable, or unusable
> in your build environment, just make sure that you add the path to the SDL
> headers to your build system's header path.  (e.g., with GCC you'd
> do an "-I" to add an additional include path)
> 
> That's the most portable way.
Guess I'll do that. :P

> sdl-config is only used with
> commandline environments.
I am on a commandline environment... xD

> i find the simplest way to get using SDL in the windows is to use 
> bloodshed dev
> c++ which has progect packages for SDL so you can download them easilly and
> then all you need is a list like
I used that once; I didn't like it, but I don't remember why... Probably
'cause I was a noob and didn't know how to use it. :@

> Not really very good advice. Experienced coders will go for
> configuration files: autoconf, Makefile or whatever VC has.
Go GNU Make! :D
Here's something I don't understand though, maybe you can fill me in - 
what exactly are autoconf and ./configure for? I know it generates the 
Makefile, I always write mine by hand... o_O

Thanks y'all for your replies!!



More information about the SDL mailing list