Mercurial > sdl-ios-xcode
view README.Watcom @ 3487:24d13328c44a
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 | 488eba319a25 |
children | 8c72321542f6 |
line wrap: on
line source
Using SDL under Windows with the OpenWatcom compiler ==================================================== Prerequisites ------------- I have done the port under Windows XP Home with SP2 installed. Windows 2000 should also be working. I'm not so sure about ancient Windows NT, since only DirectX 3 is available there. Building should be possible, but running the compiled applications will probalbly fail with SDL_VIDEODRIVER=directx. The windib driver should work, though. To compile and use the SDL with Open Watcom you will need the following: - Open Watcom compiler. I used version 1.5. The environment variables PATH, WATCOM and INCLUDE need to be set appropriately - please consult the OpenWatcom documentation and instructions given during the installation of the compiler. My setup looks like this in owvars.bat: set WATCOM=C:\watcom set INCLUDE=%WATCOM%\h;%WATCOM%\h\nt set PATH=%PATH%;%WATCOM%\binnt;%WATCOM%\binw - A fairly recent DirectX SDK. The original unmodified DX8 SDK works, as well as the minimal DirectX 7 SDK from the Allegro download site (<http://alleg.sourceforge.net/files/dx70_min.zip>). - The SDL sources from Subversion - The file Watcom-Win32.zip (now available in Subversion) Building the Library -------------------- 1) In the SDL base directory extract the archive Watcom-Win32.zip. This creates a subdirectory named 'watcom'. 2) The makefile expects the environment variable DXDIR to be set to the base directory of a DirectX SDK. I have tried a stock DX8 SDK from Microsoft as well as the minimal DirectX 7 SDK from the Allegro download site. You can also edit the makefile directly and hard code your path to the SDK on your system. I have this in my setup: set DXDIR=D:\devel\DX8_SDK 3) Enter the watcom directory and run wmake sdl 4) All tests from the test directory are working and can be built by running wmake tests Notes: The makefile offers some options to tweak the way the library is built. You have at your disposal the option to build a static (default) library, or a DLL (with tgt=dll). You can also choose whether to build a Release (default) or a Debug version (with build=debug) of the tests and library. Please consult the usage comment at the top of the makefile for usage instructions. If you specify a test target (i.e. 'wmake tests' for all tests, or selected targets like 'wmake testgl testvidinfo testoverlay2'), the tests are always freshly compiled and linked. This is done to minimise hassle when switching between library versions (static vs. DLL), because they require subtly different options. Also, the test executables are put directly into the test directory, so they can find their data files. The clean target of the makefile removes the test executables and the SDL.dll file from the test directory. To use the library in your own projects with Open Watcom, you can use the way the tests are built as base of your own build environment. The library can also be built with the stack calling convention of the compiler (-6s instead of -6r). Test applications ----------------- I've tried to make all tests work. The following table gives an overview of the current status. Testname Status ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ checkkeys + graywin + loopwave + testalpha + testbitmap + testdyngl + testerror + testfile + testgamma + testgl + testhread + testiconv - (all failed) testkeys + testlock + testoverlay + (needs 'set SDL_VIDEODRIVER=directx') testoverlay2 + (needs 'set SDL_VIDEODRIVER=directx') testpalette + testplatform + testsem + testsprite + testtimer + testver + testvidinfo + testwin ? (fading doesn't seem right) testwm + torturethread + testcdrom + testjoystick not tested threadwin + testcursor + TODO ---- There is room for further improvement: - Test joystick functionality. - Investigate fading issue in 'testwin' test. - Fix the UTF-8 support. - Adapt the makefile/object file list to support more target systems - Use "#pragma aux" syntax for the CPU info functions. Questions and Comments ---------------------- Please direct any questions or comments to me: <mailto:macpete@gmx.de> Happy Coding! Marc Peter