[SDL] Correct way of including SDL?

[KHMan]

L-28C wrote:
> 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)
>> [snip]
> 
>> 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

The best intro that I have read:
  http://sourceware.org/autobook/

The manuals for autoconf and friends are very comprehensive as
well, if you don't mind reading reference texts. It is best to
browse them entirely after reading the intro texts.

For Win32 refugees (I am one myself) seeking alternatives, I think
we tend to write Makefiles, at least in the beginning. It has the
lowest knowledge and adoption barrier. But if you want to hack at
many FLOSS projects, some knowledge of the autotools is handy.

HTH,
-- 
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia