Borland.html
1
2
3
4
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Building SDL with Borland's C++ compilers</title>
6
7
8
9
<meta name="author"
content="David Snopek and updated by Dominique Louis.">
</head>
<body>
10
<xevol @newtonave.net=""> </xevol>
11
<h1>Building SDL with Borland's C++ compilers. </h1>
12
13
14
15
16
17
18
<b> by <a href="mailto:xevol@users.sourceforge.net"> David Snopek</a></b>
and updated by <b><a href="mailto:Dominique@SavageSoftware.com.au">Dominique
Louis</a></b> ( Last updated : 30th June 2003 ).<br>
<br>
These instructions cover how to compile SDL and its included test
programs using either Borland <a href="#bcbwin">C++ Builder 5, 6 for Windows</a>,
<a href="#k3">C++ Builder for Linux ( AKA Kylix 3 )</a> or the free <a
19
href="#bccc">Borland C++ command-line compiler</a>. <br>
21
<h3> <b> Extract the files </b> </h3>
23
<p> Unzip the Borland.zip archive into <b>this</b> directory. Do not unzip
24
25
26
27
28
it into any other directory because the makefiles ( *.mak ) and project
files ( *.bpr ) use relative paths to refer to the SDL sources. This should
create a directory named "Borland" inside of the top level SDL source directory.
</p>
29
30
<h3> <b><a name="bcbwin"></a> Using Borland C++ Builder 5, 6 for Windows </b>
</h3>
32
<p> Inside of the "Borland" directory there is a "bcb6" directory that contains
33
34
35
36
37
38
39
40
a number of Builder project files. Double-click on the "libSDL.bpg" file
icon. Once Builder has started click on the "<u>P</u>rojects" menu on
the menu-bar and go down to "B<u>u</u>ild All Projects" option. <br>
This will proceed to build SDL ( with Borland's calling convention ),
SDLmain, and all the <a href="#tests">test programs</a>. Currently, all
the <a href="#tests">test programs</a> are dynamically linked to Sam Lantinga's
SDL.dll.</p>
41
42
<p><b>NOTE :</b> Borland's "lib" format and Microsoft's "lib" format are incompatible.
<br>
43
44
45
46
47
48
49
If you wish to dynamically link to the SDL library supplied by Sam Lantinga
in each release, I have created the correct *.libs for SDL 1.2.4 and they
exist in the "/lib" directory.<br>
If you would like to create the *.lib files yourself, you will need to
make use of Borland's "implib.exe" utility.<br>
</p>
50
<p><tt>IMPLIB</tt> works like this: </p>
52
<pre> IMPLIB (destination lib name) (source dll)<br></pre>
54
<p> For example,</p>
56
<pre> IMPLIB SDL.lib SDL.dll<br></pre>
58
<p>This assumes that SDL.dll was compiled with Visual C++ or similar.<br>
59
60
</p>
61
<p>To learn more about the difference between Borland's and Microsoft's *.lib
62
format please read the article <a
63
href="http://www.bcbdev.com/articles/vcdll.htm">here</a>.<br>
64
65
</p>
66
<p> <b><br>
67
68
69
70
NOTE :</b> The C++ Builder for Windows project format, is not compatible
with the Kylix 3 project format, hence the reason why they are in separate
directories.</p>
71
<h3> <b><a name="bccc"></a> Using the free Borland C++ command-line compiler
72
73
</b> </h3>
74
75
<p> The free Borland compiler can be downloaded at no charge from <a
href="http://www.borland.com/bcppbuilder/freecompiler/"> the Borland website
76
77
</a>. Make sure that it is installed and properly configured. </p>
78
<p> Open an MS-DOS Prompt. Change to the "Borland\freebcc" directory under
79
80
81
82
83
84
85
the SDL source directory. Type "make -f SDL.mak" to build SDL and "make
-f SDLmain.mak". There are also makefiles for all of the <a
href="#tests">test programs</a>, if you wish to build them. All .exes and
DLLs are created in the "test" SDL directory. Ify ou would like to create
the DLL and all the test applications, I have thrown together a basic batchfile
called "makeall.bat" which should create everything in the right order. </p>
86
<h3> <b> Output files </b> </h3>
87
88
No matter which compiler you used, three important files should have
been produced:
90
91
92
93
<li> SDL.dll ( Borland format ) </li>
<li> SDL.lib ( Borland format ) </li>
<li> SDLmain.lib ( Borland format ) </li>
95
96
97
98
Both of the *.lib files will need to be added to all the projects
that use SDL and SDL.dll must be placed some where the Windows dynamic
linker can find it (either in your project directory or on the system
path, C:\WINDOWS\SYSTEM).
99
<h3> <b><a name="k3"></a> Using Borland C++ Builder for Linux ( AKA Kylix
100
101
3 ) </b> </h3>
102
<p> Inside of the "Borland" directory there is a "k3" directory that contains
103
104
105
106
107
108
109
110
111
112
113
a number of Builder project files. Double-click on the "libSDL.bpg" file
icon. Once Builder has started click on the "<u>P</u>rojects" menu on
the menu-bar and go down to "B<u>u</u>ild All Projects" option. This will
proceed to build all the <a href="#tests">test programs</a>. <br>
Linux users do not need *.lib files as the Shared Object is linked right
into the project ( very neat actually, Windows should do this sort of thing
as it is a lot easier for the developer ). <br>
<b>NOTE :</b> The C++ Builder for Windows project format, is not
compatible with the Kylix 3 project format, hence the reason why they are
in separate directories.</p>
114
<p> On Mandrake 8.1 the shared objects for SDL are located in the /usr/lib
115
116
117
118
119
120
121
122
123
124
125
126
directory as libSDL_*.so and the Mesa OpenGL shared objects are located
in /usr/X11R6/lib as libGL*.so<br>
<br>
So if your setup is different you may need to change the project file
so that they re-link to the ones on your system.<br>
<br>
On Mandrake 8.1 the headers files are located at /usr/include/SDL/.
So if you you have not installed the development RPMs ( usually named libSDL-devel*
) for SDL ( not included ) you may have to change the include directory
within some of the projects.<br>
</p>
127
<h3> Known Problems</h3>
128
129
130
The only known problem is that I ( Dominique Louis ), was unable to
create the projects that rebuilt the SDL shared objects under Linux, due
to time constraints and my lack of intimate knowledge of Linux.
131
<h3><a name="tests"><b> Test programs </b> </a></h3>
132
133
134
135
136
137
Some of the test programs require included media files ( *.wav; *.bmp
etc ). All the test programs are now created in the "test" directory, where
the media files are ( usually ) so they should be ready to go. <br>
<br>
<br>
<br>
138
139
</body>
</html>