The never ending finding the easiest way to set up a sdl compiling envioronment on the big doze ( win )

Well, i have put in another 10-500ish hours to figuring out the definate
easiest way to get a setup for compiling SDL projects on windows for
inclusion in the wiki, as usual i havnt looked in the wiki before i post,
but all the other guides google gave just sent me round the houses and then
some, eventually i think i neede about 4 seperate guides to get things going
how i wanted.

being able to type make in cygwin and use something like notepad++ to edit
source files, like i do on linux isthe main objective, compiling all SDL
stuff on the way.

after the usual brain melt with the makefiles, eventually got one sane
enough for a basic project :wink:

SDL1.2 -

The main problem i am encountering at the moment is getting SDL_ttf to
compile and behave, i understand that there is issues with what type of
freetype library you use. cywin has some, but they dont seem to wwnat to
behave, and i downloaded others, then gave up and now i’m here.

SDL1.3 -

Do i give up on SDL_gfx and just use the GL functions? (for future projects)
Would it be possible to create GL binging functions for SDL_gfx for
backwards compatbility? the only fucncitons i like to use in SDL_Gfx is the
framerate tools.

SDL_ttf - didnt event try again yet as i cant get it going in SDL1.2 ;)----------

Neil

http://crashedcomputers.co.uk/indexgames.php

2009/11/1 Clear Computers :

being able to type make in cygwin and use something like notepad++ to edit
source files, like i do on linux isthe main objective, compiling all SDL
stuff on the way.

could cross compile… though that’s also a headache.

2009/11/1 Kenneth Bull

2009/11/1 Clear Computers :

being able to type make in cygwin and use something like notepad++ to
edit
source files, like i do on linux isthe main objective, compiling all SDL
stuff on the way.

could cross compile… though that’s also a headache.

finished it! tell me it makes sence!

SET UP A SDL 1.3 DEVELOPMENT ENVIRONMENT WITH WINDOWS IN ABOUT AN HOUR

This guide covers SDL 1.3 only, not any support libraies, if you wish to
make use of other libnraries in the SDL family you are better off using the
absolutley perfect SDL1.2. SDL1.3 is very different from SDL1.2. This is in
no way a technical document all facts are subject to change and error.

Step One - Setup Cygwin ( 10-20 mins depending on time zone and altitude )
Step Two - Get and compile SDL ( 20 - 40 mins depening on fabric of your
socks and wind speed )
Step Three - Get a sauce file editor ( 10 mins - 5 mins if there is a
halogen head lamp to hand )
Step Four - Make and run your SDL code on windows! ( anything up to and
above 47 years depending on beard shape )

Step One - Setup Cygwin

Download Cygwin setup.exe. Run it. It
will ask you where you want to put the root of the system, and where you
download packages from and to. you can delete the downloaded package files
once setup is complete. Next you will be asked what packages to download,
each set of packages has two arrows in a circle next to them, you click this
icon to toggle what is to be downloaded, if you have the time ( a copule of
hours ) and disk space and like faffing around with random crap just toggle
’all’ then click next. The bits we need are in ‘devel’ just toggling that
will take about 20 mins to download and install. You could set the actual
induvidual bits you need. But not now.

Step Two - Get and compile SDL

Double click the shiney new cygwin icon on you loverly windows desktop. A
command prompt window will appear, now type the command below then cross
your fingers, make a cup of tea, do some knitting, whatever. With a bit of
luck SDL 1.3 will compile and install.

svn co http://svn.libsdl.org/trunk/SDL && cd SDL && ./autogen.sh &&
./configure && make && make install && cd …

Step Three - Get a sauce file editor

Download and install this.
It has realivley good C editing facilities.

Step Four - Make and run your SDL code on windows!

Download this,
extract it to your cygwin/home/user directory, then run this command…

cd blahsdl && make

Then, you can run it using the command ( from inside blahsdl directory ),
you may need to copy the SDL.dll from inside the SDL directory to the same
folder.

./sdlblah.exe

I think using a crossplatform IDE is the easiest way to get going with
SDL. If you’re only interested in part of SDL_gfx, why not strip it
out and make a new library? And if you think Make is dumb, send me an
email off-list.

Jonny DOn Sun, Nov 1, 2009 at 4:33 PM, Neil White wrote:

2009/11/1 Kenneth Bull

2009/11/1 Clear Computers :

being able to type make in cygwin and use something like notepad++ to
edit
source files, like i do on linux isthe main objective, compiling all SDL
stuff on the way.

could cross compile… though that’s also a headache.

finished it! tell me it makes sence!

SET UP A SDL 1.3 DEVELOPMENT ENVIRONMENT WITH WINDOWS IN ABOUT AN HOUR

This guide covers SDL 1.3 only, not any support libraies, if you wish to
make use of other libnraries in the SDL family you are better off using the
absolutley perfect SDL1.2. SDL1.3 is very different from SDL1.2. This is in
no way a technical document all facts are subject to change and error.

Step One - Setup Cygwin ( 10-20 mins depending on time zone and altitude )
Step Two - Get and compile SDL ( 20 - 40 mins depening on fabric of your
socks and wind speed )
Step Three - Get a sauce file editor ( 10 mins - 5 mins if there is a
halogen head lamp to hand )
Step Four - Make and run your SDL code on windows! ( anything up to and
above 47 years depending on beard shape )

Step One - Setup Cygwin

Download Cygwin setup.exe. Run it. It
will ask you where you want to put the root of the system, and where you
download packages from and to. you can delete the downloaded package files
once setup is complete. Next you will be asked what packages to download,
each set of packages has two arrows in a circle next to them, you click this
icon to toggle what is to be downloaded, if you have the time ( a copule of
hours ) and disk space and like faffing around with random crap just toggle
’all’ then click next. The bits we need are in ‘devel’ just toggling that
will take about 20 mins to download and install. You could set the actual
induvidual bits you need. But not now.

Step Two - Get and compile SDL

Double click the shiney new cygwin icon on you loverly windows desktop. A
command prompt window will appear, now type the command below then cross
your fingers, make a cup of tea, do some knitting, whatever. With a bit of
luck SDL 1.3 will compile and install.

svn co http://svn.libsdl.org/trunk/SDL && cd SDL && ./autogen.sh &&
./configure && make && make install && cd …

Step Three - Get a sauce file editor

Download and install this.
It has realivley good C editing facilities.

Step Four - Make and run your SDL code on windows!

Download this,
extract it to your cygwin/home/user directory, then run this command…

cd blahsdl && make

Then, you can run it using the command ( from inside blahsdl directory ),
you may need to copy the SDL.dll from inside the SDL directory to the same
folder.

./sdlblah.exe


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

2009/11/1 Jonathan Dearborn

I think using a crossplatform IDE is the easiest way to get going with
SDL. If you’re only interested in part of SDL_gfx, why not strip it
out and make a new library? And if you think Make is dumb, send me an
email off-list.

i know i very often makes little sense when i am posting to this mail list
often my english is very bad being english and everything

have yo done OSX cross compile it this possible yet?

is it yet possible for me to turf out a chunk of code and have a cross
compile SDL turf me out a binary for every ststem i want?

FYI, I typically build using Visual Studio for development and
debugging, but cross-compile from Mac OS X for the final release.
That works really well for me, since I get the nice integrated
debugging on the one hand, and avoid nasty manifest and C runtime
dependencies on the other.

See ya!On Mon, Nov 2, 2009 at 3:49 AM, Neil White wrote:

2009/11/1 Jonathan Dearborn

I think using a crossplatform IDE is the easiest way to get going with
SDL. ?If you’re only interested in part of SDL_gfx, why not strip it
out and make a new library? ?And if you think Make is dumb, send me an
email off-list.

i know i very often makes little sense when i am posting to this mail list
often my english is very bad being english and everything

have yo done OSX cross compile it this possible yet?

is it yet possible for me to turf out a chunk of code and have a cross
compile SDL turf me out a binary for every ststem i want?


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


-Sam Lantinga, Founder and President, Galaxy Gameworks LLC