Since gcc(egcs) exists now for BeOS Intel, is there an SDL version of
Executor planned?
There is already an SDL version of Executor, however there is much more
to Executor than the graphics and sound code. So, to answer your question,
it’s not being worked on, but we’re tossing the idea around.
I’m going to CC this to Cliff who may be able to comment directly.
Also, is MMX support enabled in BeOS?
Not yet.
Does anyone want me to do a build of SDL with gcc?
It doesn’t build. There are linking issues using the GNU ld with C++ objects
under BeOS.
However, code built with gcc can link with SDL built with the Metrowerks
compiler, so large C projects using the SDL API will work under BeOS.
I tested this with the aliens example program and DOOM, though DOOM built
with gcc has a major bug which I believe is compiler-related.
Sam> David Sowsy wrote:
>> Since gcc(egcs) exists now for BeOS Intel, is there an SDL
>> version of Executor planned?
Sam> There is already an SDL version of Executor, however there is
Sam> much more to Executor than the graphics and sound code. So,
Sam> to answer your question, it's not being worked on, but we're
Sam> tossing the idea around. I'm going to CC this to Cliff who
Sam> may be able to comment directly.
ARDI doesn’t want to officially say anything about BeOS. Unofficially
here’s what’s going on. So far, Executor has had a number of
different front ends: native X, NEXTSTEP/OPENSTEP, DOS, svgalib,
Win32-DIB, and Win32/SDL. We’ve dropped the NEXTSTEP/OPENSTEP and
Win32-DIB implementations and currently ship native X, DOS, svgalib
and Win32/SDL.
SDL appears to be shaping up sufficiently well enough that starting
soon (perhaps this week), we’ll likely switch to X/SDL. Once that
transition is nicely made, I suspect we’ll do a skunk-works port to
BeOS. That is still probably a month or two away. The nice thing
about this arrangement is that if SDL/BeOS is rock-solid the
skunk-works version of Executor/BeOS would suddenly be just as stable
as all the other versions of Executor.
Have you had success with audio with SDL under x86 BeOS? Most of the examples
run fine (a few problems when apps exit but nothing major) but anything with
sound (aliens for example) crashes for me. Actually, I should qualify that. The
graphics in aliens run fine, but I don’t get any sound and an error message that
says the app must be closed because it had an unrecoverable error (which I assume
is the audio thread) shows up. Sure wish there was a source-level debugger for
x86 BeOS. It would make finding the problem a lot easier.
Since gcc(egcs) exists now for BeOS Intel, is there an SDL version of
Executor planned?
There is already an SDL version of Executor, however there is much more
to Executor than the graphics and sound code. So, to answer your question,
it’s not being worked on, but we’re tossing the idea around.
I’m going to CC this to Cliff who may be able to comment directly.
Also, is MMX support enabled in BeOS?
Not yet.
Does anyone want me to do a build of SDL with gcc?
It doesn’t build. There are linking issues using the GNU ld with C++ objects
under BeOS.
However, code built with gcc can link with SDL built with the Metrowerks
compiler, so large C projects using the SDL API will work under BeOS.
I tested this with the aliens example program and DOOM, though DOOM built
with gcc has a major bug which I believe is compiler-related.
