Using SDL with Code::Blocks - Revision history

MaxwellM: /* The Process */

2006-08-20T13:53:53Z

The Process

MaxwellM: /* The Process */

2006-08-20T13:53:02Z

The Process

Artojon: edit category

2006-07-08T12:40:17Z

edit category

Sethjackson: If only I could type. :P

2006-04-11T20:25:18Z

If only I could type. :P

Sethjackson at 20:24, 11 April 2006

2006-04-11T20:24:46Z

Sethjackson at 01:54, 9 April 2006

2006-04-09T01:54:54Z

Thomas at 15:28, 6 February 2006

2006-02-06T15:28:37Z

Frobozz: SDL is up to 1.2.9 - Devpaks are still 1.2.8

2005-10-07T06:37:56Z

SDL is up to 1.2.9 - Devpaks are still 1.2.8

Thomas: /* The Process */

2005-08-25T08:56:05Z

The Process

Thomas: /* The Process */

2005-08-25T08:52:35Z

The Process

@@ Line 24: / Line 24: @@
 #Download [http://www.libsdl.org/release/SDL-devel-1.2.9-mingw32.tar.gz SDL-devel-1.2.9-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.9 download page]. There are binary packages for several Linux distributions, too (<tt>rpm</tt> may have problems downloading directly from libsdl.org, use <tt>wget</tt> to get the packages in that case).
 #Decompress the archive
-#Copy <tt>SDL.dll</tt> from inside the <tt>bin</tt> folder to the your compilers bin directory (ie <tt>C:\Mingw\bin</tt>. This allows the compiler to find the dll at runtime time without having to put it in the same folder as your program or in the windows folder.
+#Copy <tt>SDL.dll</tt> from inside the <tt>bin</tt> folder to the your compilers bin directory (ie <tt>C:\Mingw\bin</tt>) This allows the compiler to find the dll at runtime time without having to put it in the same folder as your program or in the windows folder.
 #Copy the contents of <tt>lib</tt> to your compiler's lib folder. If MinGW is installed under <tt>C:\MinGW</tt>, then this will be <tt>C:\MinGW\lib</tt>.
 #Copy the complete folder <tt>SDL</tt> from inside the folder <tt>include</tt> to your compiler's include directory (for example <tt>C:\MinGW\include</tt>). Be sure to copy the ''folder'', not the individual files.

@@ Line 24: / Line 24: @@
 #Download [http://www.libsdl.org/release/SDL-devel-1.2.9-mingw32.tar.gz SDL-devel-1.2.9-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.9 download page]. There are binary packages for several Linux distributions, too (<tt>rpm</tt> may have problems downloading directly from libsdl.org, use <tt>wget</tt> to get the packages in that case).
 #Decompress the archive
-#Copy <tt>SDL.dll</tt> from inside the <tt>bin</tt> folder to where you keep your dll files (could be <tt>C:\MinGW\dll</tt> or <tt>C:\MinGW\lib</tt>, whatever).
+#Copy <tt>SDL.dll</tt> from inside the <tt>bin</tt> folder to the your compilers bin directory (ie <tt>C:\Mingw\bin</tt>. This allows the compiler to find the dll at runtime time without having to put it in the same folder as your program or in the windows folder.
 #Copy the contents of <tt>lib</tt> to your compiler's lib folder. If MinGW is installed under <tt>C:\MinGW</tt>, then this will be <tt>C:\MinGW\lib</tt>.
 #Copy the complete folder <tt>SDL</tt> from inside the folder <tt>include</tt> to your compiler's include directory (for example <tt>C:\MinGW\include</tt>). Be sure to copy the ''folder'', not the individual files.

← Older revision		Revision as of 12:40, 8 July 2006
Line 1:		Line 1:
−	[[Category:~~Installation\Build Instructions~~]]	+	[[Category:User Documentation]]

	Written by Thomas.		Written by Thomas.

← Older revision		Revision as of 20:25, 11 April 2006
Line 1:		Line 1:
−	[[Category:Installation\Build ~~Isntructions~~]]	+	[[Category:Installation\Build Instructions]]

	Written by Thomas.		Written by Thomas.

@@ Line 1: / Line 1: @@
-[[Category:Graphical Toolkits]]
+[[Category:Installation\Build Isntructions]]
-[[Category:Build Intructions]]
 Written by Thomas.
 Original idea by [http://www.ubergeekultd.com Ubergeek, ultd].

@@ Line 7: / Line 7: @@
 =="The Good, the Bad, and the Ugly" - Setting up SDL==
-This article deals with [[SDL]] using [[CodeBlocks:About|Code::Blocks]] with the [http://www.mingw.org MinGW compiler], however the same steps will likely work with a different compiler (such as MSVC2003 toolkit) or under Linux, too (Linux users will of course not worry about DirectX).
+This article deals with [http://www.libsdl.org/ SDL] using [[CodeBlocks:About|Code::Blocks]] with the [http://www.mingw.org MinGW compiler], however the same steps will likely work with a different compiler (such as MSVC2003 toolkit) or under Linux, too (Linux users will of course not worry about DirectX).
 There are many ways to get the necessary libraries and include files to set up SDL to be used with Code::Blocks, each of them having its own advantages and disadvantages. In  memory of Sergio Leone's best movie, I will call these "the Good", "the Bad", and "the Ugly".<br />

← Older revision		Revision as of 15:28, 6 February 2006
Line 1:		Line 1:
		+	[[Category:Graphical Toolkits]]
		+	[[Category:Build Intructions]]
		+	[[Category:Tutorials]]
	Written by Thomas.		Written by Thomas.
	Original idea by [http://www.ubergeekultd.com Ubergeek, ultd].		Original idea by [http://www.ubergeekultd.com Ubergeek, ultd].

@@ Line 20: / Line 20: @@
 #Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)<br />
 ===The Process===
-#Download [http://www.libsdl.org/release/SDL-devel-1.2.8-mingw32.tar.gz SDL-devel-1.2.8-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]. There are binary packages for several Linux distributions, too (<tt>rpm</tt> may have problems downloading directly from libsdl.org, use <tt>wget</tt> to get the packages in that case).
+#Download [http://www.libsdl.org/release/SDL-devel-1.2.9-mingw32.tar.gz SDL-devel-1.2.9-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.9 download page]. There are binary packages for several Linux distributions, too (<tt>rpm</tt> may have problems downloading directly from libsdl.org, use <tt>wget</tt> to get the packages in that case).
 #Decompress the archive
 #Copy <tt>SDL.dll</tt> from inside the <tt>bin</tt> folder to where you keep your dll files (could be <tt>C:\MinGW\dll</tt> or <tt>C:\MinGW\lib</tt>, whatever).
@@ Line 30: / Line 30: @@
 ===Alternative===
-Code::Blocks comes with support for reading '''.DevPak''' files of late. This allows for an even more comfortable setup. Recent DevPaks (1.2.8) for SDL, SDL-mixer, and SDL-ttf can be found at [http://www.devpaks.org/category.php?category=SDL http://www.devpaks.org/category.php?category=SDL].<br />
+Code::Blocks comes with support for reading '''.DevPak''' files of late. This allows for an even more comfortable setup. DevPaks (1.2.8) for SDL, SDL-mixer, and SDL-ttf can be found at [http://www.devpaks.org/category.php?category=SDL http://www.devpaks.org/category.php?category=SDL].<br />
 '''Important:''' Please do note that the packages at devpaks.org are not original packages created by the SDL team. Be aware that devpaks.org theoretically allows anyone to upload anything under the name SDL. Although I know of no case of malware being distributed over this channel, this is a potential risk you have to be aware of.
@@ Line 51: / Line 51: @@
 ===The Process===
-#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]
+#Download [http://www.libsdl.org/release/SDL-1.2.9.tar.gz SDL-1.2.9.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.9 download page]
-#Decompress the archive somewhere (I will assume <tt>C:\SDL-1.2.8</tt> from now on)
+#Decompress the archive somewhere (I will assume <tt>C:\SDL-1.2.9</tt> from now on)
-#Inside <tt>C:\SDL-1.2.8</tt>, locate the file <tt>VisualC.zip</tt>, decompress it, and open the workspace <tt>C:\SDL-1.2.8\VisualC\SDL.dsw</tt>
+#Inside <tt>C:\SDL-1.2.9</tt>, locate the file <tt>VisualC.zip</tt>, decompress it, and open the workspace <tt>C:\SDL-1.2.9\VisualC\SDL.dsw</tt>
 #As of RC1-1, Code::Blocks does not parse Visual-C projects 100% correctly, so you have to check that link libraries and include path are specified correctly.<br />
 #*SDL needs <tt>winmm</tt>, <tt>gdi32</tt>, and <tt>dxguid</tt>.
 #*Also, you have to add the <tt>include</tt> directory inside the SDL source directory to compiler paths.
 #Rebuild all (~3 minutes)
-#Inside <tt>C:\SDL-1.2.8\VisualC\SDL</tt> and <tt>C:\SDL-1.2.8\VisualC\SDLmain</tt>, you will find the DLLs inside the <tt>Debug</tt> and <tt>Release</tt> folders. Copy the DLLs to where you want to keep them and the static libraries to your compiler's <tt>lib</tt> folder.
+#Inside <tt>C:\SDL-1.2.9\VisualC\SDL</tt> and <tt>C:\SDL-1.2.9\VisualC\SDLmain</tt>, you will find the DLLs inside the <tt>Debug</tt> and <tt>Release</tt> folders. Copy the DLLs to where you want to keep them and the static libraries to your compiler's <tt>lib</tt> folder.
-#Make a folder <tt>SDL</tt> inside your compiler's include directory. Copy all files from <tt>C:\SDL-1.2.8\include</tt> into that directory
+#Make a folder <tt>SDL</tt> inside your compiler's include directory. Copy all files from <tt>C:\SDL-1.2.9\include</tt> into that directory
 [[Image:Compile sdl include libraries.png|Include directory and link libraries for building SDL in Code::Blocks]]
@@ Line 75: / Line 75: @@
 *Some of the files in the archive may be read-only for some obscure reason. <tt>make</tt> will choke when trying to overwrite these.
 ===The Process===
-#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]
+#Download [http://www.libsdl.org/release/SDL-1.2.9.tar.gz SDL-1.2.9.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.9 download page]
-#Decompress the archive somewhere (I will assume <tt>C:\SDL-1.2.8</tt> from now on). The path may not contain any spaces.
+#Decompress the archive somewhere (I will assume <tt>C:\SDL-1.2.9</tt> from now on). The path may not contain any spaces.
 #Run <tt>./configure</tt> along with all options that you wish. (~5-6 minutes)
 #*<tt>./configure --help</tt> shows all possible packages to include as well as all available options

@@ Line 26: / Line 26: @@
 #Copy the complete folder <tt>SDL</tt> from inside the folder <tt>include</tt> to your compiler's include directory (for example <tt>C:\MinGW\include</tt>). Be sure to copy the ''folder'', not the individual files.
 #Optionally, copy <tt>SDL.dll</tt> to <tt>C:\Windows</tt>, too. This will save you from copying the dll to each and every project directory while developing. Be cautious, however, not to find yourself in [http://en.wikipedia.org/wiki/DLL_hell DLL hell] afterwards.
-#Screw the rest
+#Screw the rest (in particular, forget about sdlconfig - it will not work)
 It is of course possible to keep the library and include files in different locations than the ones stated above. In that case, you will have to add those locations to the compiler options. However, be sure ''not'' to add the <tt>SDL</tt> folder to include paths, but its ''parent folder'', as all SDL programs expect the headers to be inside a separate <tt>SDL</tt> folder.
 ===Alternative===
 Code::Blocks comes with support for reading '''.DevPak''' files of late. This allows for an even more comfortable setup. Recent DevPaks (1.2.8) for SDL, SDL-mixer, and SDL-ttf can be found at [http://www.devpaks.org/category.php?category=SDL http://www.devpaks.org/category.php?category=SDL].<br />

@@ Line 92: / Line 92: @@
 #Open Build options and make sure the necessary libraries are included.
 #*You have to link with <tt>mingw32</tt>, <tt>SDL</tt>, and <tt>SDLmain</tt> to use SDL. The template should already include these, but you may want to check.
-#*Also, you may want to add <tt>-mwindows</tt> to "Other linker options" to prevent a DOS window from showing (actually this is controlled by the build target type: "console" or "GUI").
+#*If you have built your libs from MSYS, you can always run <tt>bash sdl-config --libs</tt> from SDL's source directory when in doubt. This will output the correct libraries to link with (including <tt>-mwindows</tt>, which you can omit, see next point). However, do ''not'' get tempted to derive your include paths from <tt>sdl-config</tt>, too. Although this is technically the correct way to do it, at least on Windows, these are complete garbage.
 #Compile and run