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 1628 - Support for dual-compiler nature of Haiku on x86
Summary: Support for dual-compiler nature of Haiku on x86
Status: RESOLVED ENDOFLIFE
Alias: None
Product: SDL
Classification: Unclassified
Component: build (show other bugs)
Version: HG 1.2
Hardware: x86 Haiku
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-24 12:59 UTC by PulkoMandy
Modified: 2015-08-25 09:38 UTC (History)
0 users

See Also:


Attachments
Modified sdl-config that handles dual-compiler setup for Haiku. (1.56 KB, application/octet-stream)
2012-10-24 12:59 UTC, PulkoMandy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description PulkoMandy 2012-10-24 12:59:00 UTC
Created attachment 978 [details]
Modified sdl-config that handles dual-compiler setup for Haiku.

Haiku tries to keep binary compatibility with BeOS. This involves building the system with gcc2 because of C++ ABI breakage. Most applications, however, need gcc4 to build properly.
So Haiku has a system called hybrid builds, where both compilers are available. Each of them comes with its own set of libs.

The problem is sdl-config doesn't handle that. I made a modified version of it that will use the setgcc command and use the right path for the libs in all cases.

I'm not sure how to integrate this to SDL build system. The script that generates sdl-config does not look flexible enough.
SDL 2.0 likely needs the same kind of fix, but I haven't looked at it yet.
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.