Mercurial > sdl-ios-xcode

view Borland.html @ 3487:24d13328c44a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Eric Wing to Sam, hfutrell This one is quite puzzling. I found a partial workaround, but I don't fully understand the reasons yet. First, the console is complaining about not finding a nib for MainWindow. I tried removing the entry for this in the info.plist, and the message went away, but it didn't really change anything. Second, I stepped through this with the debugger and broke up some lines. It seems that the basic act of calling view = [SDL_uikitopenglview alloc]; or even view = [SDL_uikitview alloc] will crash the program. The debugger messages plus the stack trace make me think it's not finding the SDL_uikitview classes for some reason. But I don't understand why this would be. view = [UIView alloc] will not crash the program. For kicks, I added a new definition of a class called SDL_object which subclasses NSObject in the same files as SDL_uikitopenglview and then call view = [SDL_object alloc]; This does not crash the program. So, then I modified SDL_object to subclass UIView. No crash. Next, I made SDL_object subclass UIView<UITextFieldDelegate> . This crashes. So it is the act of conforming to the UITextFieldDelegate protocol that is crashing things. I don't understand why it would crash on alloc though. I'm guessing either a delegate needs to be set somewhere or one of the required methods needs to be implemented. But in the former case, I would not expect a crash, but a silent message to nil and something else doesn't work. And in the latter case, I would expect a compiler warning and an exception thrown instead of a crash. Anyway, my temporary workaround is to change the interface declaration for SDL_uikitview to look like: #if SDL_IPHONE_KEYBOARD @interface SDL_uikitview : UIView<UITextFieldDelegate> { #else @interface SDL_uikitview : UIView { #endif And then disable the keyboard support in the SDL_config_iphoneos.h file. /* enable iPhone keyboard support */ #define SDL_IPHONE_KEYBOARD 0 -Eric On Nov 23, 2009, at 1:43 AM, Sam Lantinga wrote: > I ran into a blocking startup crash with the Happy demo on iPhone OS 3.1.2 on my new iPhone: > > #0 0x323fea14 in _class_isInitialized > #1 0x323fea68 in _class_initialize > #2 0x32403e92 in prepareForMethodLookup > #3 0x32401244 in lookUpMethod > #4 0x323fea10 in _class_lookupMethodAndLoadCache > #5 0x323fe746 in objc_msgSend_uncached > #6 0x323feb26 in _class_initialize > #7 0x323fea58 in _class_initialize > #8 0x32403e92 in prepareForMethodLookup > #9 0x32401244 in lookUpMethod > #10 0x323fea10 in _class_lookupMethodAndLoadCache > #11 0x323fe746 in objc_msgSend_uncached > #12 0x000554dc in UIKit_GL_CreateContext at SDL_uikitopengles.m:103 > #13 0x0004f89e in SDL_GL_CreateContext at SDL_video.c:3155 > #14 0x000579e8 in GLES_CreateRenderer at SDL_renderer_gles.c:282 > #15 0x0004d7b8 in SDL_CreateRenderer at SDL_video.c:1509 > #16 0x00002bc2 in SDL_main at happy.c:156 > #17 0x000571b2 in -[SDLUIKitDelegate postFinishLaunch] at > SDL_uikitappdelegate.m:77 > #18 0x313f9ef2 in __NSFireDelayedPerform > #19 0x32567bb2 in CFRunLoopRunSpecific > #20 0x3256735c in CFRunLoopRunInMode > #21 0x32912cbe in GSEventRunModal > #22 0x32912d6a in GSEventRun > #23 0x32b6276e in -[UIApplication _run] > #24 0x32b61472 in UIApplicationMain > #25 0x00057088 in main at SDL_uikitappdelegate.m:50 > > Any ideas? > > See ya! > -- > -Sam Lantinga, Founder and President, Galaxy Gameworks LLC
author Sam Lantinga <slouken@libsdl.org>
date Tue, 24 Nov 2009 08:12:32 +0000
parents de622b7108bf
children
line wrap: on
line source

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title>Building SDL with Borland's C++ compilers</title>
                                  
  <meta name="author"
 content="David Snopek and updated by Dominique Louis.">
</head>
  <body>
     <xevol @newtonave.net="">      </xevol>     
<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> ( 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
 href="#bccc">Borland C++ command-line compiler</a>. <br>
            
<h3> <b> Extract the files </b> </h3>
            
<p> Unzip the Borland.zip archive into <b>this</b> directory.  Do not unzip 
  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>
            
<h3> <b><a name="bcbwin"></a> Using Borland C++ Builder 5, 6 for Windows </b>
</h3>
            
<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>
     
<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>
   </p>
     
<p><tt>IMPLIB</tt> works like this: </p>
       
<pre>    IMPLIB (destination lib name) (source dll)<br></pre>
       
<p> For example,</p>
       
<pre>    IMPLIB SDL.lib SDL.dll<br></pre>
     
<p>This assumes that SDL.dll was compiled with Visual C++ or similar.<br>
   </p>
     
<p>To learn more about the difference between Borland's and Microsoft's *.lib 
 format please read the article <a
 href="http://www.bcbdev.com/articles/vcdll.htm">here</a>.<br>
   </p>
     
<p>  <b><br>
   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>
            
<h3> <b><a name="bccc"></a> Using the free Borland C++ command-line compiler 
 </b> </h3>
            
<p> The free Borland compiler can be downloaded at no charge from <a
 href="http://www.borland.com/bcppbuilder/freecompiler/"> the  Borland website 
  </a>.  Make sure that it is installed and properly configured. </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. 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 
 been  produced:        
<ul>
      	<li> SDL.dll ( Borland format ) </li>
      	<li> SDL.lib&nbsp;( Borland format ) </li>
      	<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).       
<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>
   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>&nbsp;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>
           
<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>
       <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>
     
<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.     
<h3><a name="tests"><b> Test programs </b> </a></h3>
   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>