*** empty log message ***

--HG--
extra : convert_revision : svn%3Ac70aab31-4412-0410-b14c-859654838e24/trunk%40643

Borland.html

@@ -11,10 +11,10 @@
 <h1>Building SDL with Borland's C++ compilers. </h1>
       <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>.<br>
+  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>, 
+       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
  href="#bccc">Borland C++ command-line compiler</a>. <br>
             
@@ -31,20 +31,20 @@ create a directory named "Borland" inside of the top level SDL source directory.
             
 <p> Inside of the "Borland" directory there is a "bcb6" directory that contains 
   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>
+  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>
      
 <p><b>NOTE :</b> Borland's "lib" format and Microsoft's "lib" format are incompatible.
 &nbsp;<br>
    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>
+   If you would like to create the *.lib files yourself, you will need to 
+make  use of Borland's "implib.exe" utility.<br>
    </p>
      
 <p><tt>IMPLIB</tt> works like this: </p>
@@ -78,7 +78,10 @@ directories.</p>
 <p> Open an MS-DOS Prompt.  Change to the "Borland\freebcc" directory under 
   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. </p>
+ 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>
             
 <h3> <b> Output files </b> </h3>
        No matter which compiler you used, three important files should have 
@@ -89,19 +92,18 @@ been  produced:
       	<li> SDLmain.lib&nbsp;( Borland format ) </li>
            
 </ul>
-     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). 
-   
+       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).       
 <h3> <b><a name="k3"></a> Using Borland C++ Builder for Linux ( AKA Kylix 
  3 ) </b> </h3>
               
 <p> Inside of the "Borland" directory there is a "k3" directory that contains 
   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>.&nbsp;<br>
+  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>.&nbsp;<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>
@@ -110,8 +112,8 @@ compatible with the Kylix  3 project format, hence the reason why they are
  in separate directories.</p>
            
 <p> On Mandrake 8.1 the shared objects for SDL are located in the /usr/lib 
- directory as libSDL_*.so and the Mesa OpenGL shared objects are located in
- /usr/X11R6/lib as libGL*.so<br>
+  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>
@@ -123,15 +125,15 @@ within  some of the projects.<br>
    </p>
      
 <h3> Known Problems</h3>
-   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.   
+     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.     
 <h3><a name="tests"><b> Test programs </b> </a></h3>
- Some of the test programs require included media files ( *.wav; *.bmp etc 
- ).  Before trying to run any of the  test programs, copy these media files 
- from the "tests/" directory into the Borland build directory that you extracted 
- the project files to.  <br>
+   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>
 </body>
 </html>
-