"SDL.h" or "SDL/SDL.h"

In my tutorials I use #include “SDL/SDL.h” to include the header files. This
week I adjusted my tutorials to accomidate the fact that the Win32 MinGW package
now no longer has a SDL subfolder.

I’m wondering, does the Linux RPM no longer put the headers in an /include/SDL
subfolder? I tried to check myself but the RPM refused to install.

I’ve always liked putting all the SDL headers in a seperate folder.

The “official” SDL way is #include “SDL.h”, then use sdl-config --cflags to tell gcc the correct directory where the SDL includes
are.On 3/14/06, Lazy Foo’ wrote:

In my tutorials I use #include “SDL/SDL.h” to include the header files. This
week I adjusted my tutorials to accomidate the fact that the Win32 MinGW package
now no longer has a SDL subfolder.

I’m wondering, does the Linux RPM no longer put the headers in an /include/SDL
subfolder? I tried to check myself but the RPM refused to install.

I’ve always liked putting all the SDL headers in a seperate folder.

  • SR

linux installs default to ${includedir}/SDL which on distros pretty much
always translates to /usr/include/SDL

smart packages shouldnt care … they should just do ‘#include <SDL.h>’ and
then add the output of sdl-config --cflags to their build system …
-mikeOn Tuesday 14 March 2006 22:51, Lazy Foo’ wrote:

I’m wondering, does the Linux RPM no longer put the headers in an
/include/SDL subfolder? I tried to check myself but the RPM refused to
install.

Hello !

It was always told here to use #include "SDL.h"
As that would be the most portable.

CU