We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1504

Summary: OpenWatcom 1.9 builds are broken (includes fix)
Product: SDL Reporter: Kostas Michalopoulos <badsectoracula>
Component: buildAssignee: Sam Lantinga <slouken>
Status: RESOLVED ENDOFLIFE QA Contact: Sam Lantinga <slouken>
Severity: major    
Priority: P2    
Version: 1.2.15   
Hardware: x86   
OS: Windows (All)   

Description Kostas Michalopoulos 2012-05-23 18:58:14 UTC 
Building SDL 1.2.15 from source using OpenWatcom 1.9 is broken. Two files need to be modified:

1. The SDL_config_win32.h file must change line ~30 to check __WATCOMC__ macro (recent OpenWatcom versions include stdint):

  #if defined(__GNUC__) || defined(__DMC__) || defined(__WATCOMC__)


2. The watcom/makefile (inside the Watcom-Win32.zip file) must change direct calls to wlink from

  wlink ...

to indirect from cmd

  cmd /c wlink ...

otherwise wlink fails to create the dll file.
Comment 1 Ryan C. Gordon 2015-08-25 09:38:23 UTC 
Hello, and sorry if you're getting several copies of this message by email, since we are closing many bugs at once here.

We have decided to mark all SDL 1.2-related bugs as RESOLVED ENDOFLIFE, as we don't intend to work on SDL 1.2 any further, but didn't want to mark a large quantity of bugs as RESOLVED WONTFIX, to clearly show what was left unattended to and make it easily searchable.

Our current focus is on SDL 2.0.

If you are still having problems with an ENDOFLIFE bug, your absolute best option is to move your program to SDL2, as it will likely fix the problem by default, and give you access to modern platforms and tons of super-cool new features.

Failing that, we _will_ accept small patches to fix these issues, and put them in revision control, although we do not intend to do any further official 1.2 releases.

Failing that, please feel free to contact me directly by email (icculus@icculus.org) and we'll try to find some way to help you out of your situation.

Thank you,
--ryan.