At 9:00 Uhr -0600 24.02.2002, David Leimbach wrote:
At 1:38 Uhr +0000 24.02.2002, Dominique Louis wrote:
I only ever get static to work so I never see dylibs come out of the
automake based SDL build on OS X. Is this different in CVS? [I
need to reverify this but I distinctly remember wanting to use
frameworks as a result of failed attempts to build a shared library
of the following: SDL and SDL_image].
You can produce shared libs with them, but you have to make sure you
use the right version of libtool. The non-CVS version ship with a
libtool version that can’t build dynamic libs on OS X. If you use
e.g. libtool 1.4.2 with CVS, or the patched ltmain.sh / ltconfig for
1.3.5 (which we provide at
works. In Fink I used this for the SDL packages (see
However, let me say this now: I don’t think one should use shared
libraries for most apps that use SDL. That is, it’s OK to use SDL
shared libs during development, but when you ship it, do yourself and
your customers a favor and static link SDL.
Hm, AFAIK the chance to see Kylix on OS X are pretty slim,
especially in a state where it is usable to produce “real” MacOS X
apps (i.e. giving you access more than just the core BSD APIs). Do
you have any reason to believe differently? I’m just curious.
I think Max is correct unless someone has an inside information we
don’t. The ability to use Cocoa will require objective-c and
frameworks support [maybe it can be done with Cocoa’s other native
language - java].
That’s not fully true. There exists Cocoa wrappers for Tcl/Tk
(provided by Apple!), and internally they have some Perl wrappers
(though this is not release, since the guy who hacked it up has had
no time so far to publish it - they use this for the internal OS
build system). Also, I think I saw some neat Ruby wrappers at
SourceForge. So it is possible, although I think that you loose a lot
elegance if you code in something different from Objective C. I just
love that language =)
If you aren’t using Cocoa you are using Carbon to code for Aqua.
Cocoa is, by things I have read on apple’s site, going to be only
API of the two that they continue to support and develop in the long
term. Carbon is there to get your app to OS X quickly while you
work on Cocoa-ifying it as far as I can see.
Nah, not the full truth… Carbon isn’t going away for a long time.
At least not for the next 5-10 years. And the new Carbon APIs are
themselves quite nice. Though I personally almost only code in Cocoa
these days, it’s just a programmers dream come true
Now I suppose you could write Kylix to use QT on OS X but even QT
uses Carbon and then you are simply adding another layer of
Kylix->C+±>QT->Carbon->Quartz. So Kylix doesn’t seem a likely
candidate for OSX unless they wrap up the whole Carbon or Cocoa API
in Kylix [pascal-like] code [this is presuming that Kylix needs a
special ABI to call on Cocoa/Carbon functions].
Blah… this all has nothing to do with SDL directly.
Yes =)>On Sunday, February 24, 2002, at 07:34 AM, Max Horn wrote:
phone: (+49) 6151-494890