OSX.1 and libSDL 1.2

Hi all…

I just upgraded my Powerbook G4 to OSX.1, and now i can’t get the new
project builder (or straight makefiles) to link properly with libSDL 1.2.

I tried reinstalling libSDL, thinking that perhaps installing the 10.1
developer tools munged something along the way, but to no avail. It
still was borked.

I imagine that this problem has been solved already, but i couldn’t find
any information either on the libSDL pages, or the mailing list archives
that addresses this problem.

Can anyone help?

-j–
Scott “Jerry” Lawrence
@Scott_Jerry_Lawrence

For all of your Cheese Weasel needs… http://www.cheeseweasel.com

At 0:20 Uhr -0400 14.10.2001, Scott Jerry Lawrence wrote:

Hi all…

I just upgraded my Powerbook G4 to OSX.1, and now i can’t get the
new project builder (or straight makefiles) to link properly with
libSDL 1.2.

I tried reinstalling libSDL, thinking that perhaps installing the
10.1 developer tools munged something along the way, but to no
avail. It still was borked.

I imagine that this problem has been solved already, but i couldn’t
find any information either on the libSDL pages, or the mailing list
archives that addresses this problem.

Can anyone help?

You should get the latest CVS version which fixes this and other OS X
issues. Or wait till 1.2.3 is released :slight_smile:

If you are really in a hurry, then I think adding several frameworks
to the SDL project should help you (namely, Carbon.framework and
Cocoa.framework).

Max–

Max Horn
Software Developer

email: mailto:Max_Horn
phone: (+49) 6151-494890

At 0:20 Uhr -0400 14.10.2001, Scott Jerry Lawrence wrote:

Can anyone help?

You should get the latest CVS version which fixes this and other OS X
issues. Or wait till 1.2.3 is released :slight_smile:

I just tried this. I downloaded the 1.2 tarball from
[http://www.libsdl.org/cvs.html], i followed the directions in the
readme (./configure, make, make install), which all worked cleanly and
flawlessly (cheers!) then i went into project builder, created a new SDL
Framework based project, and it had the same linking problem.

If you are really in a hurry, then I think adding several frameworks to
the SDL project should help you (namely, Carbon.framework and
Cocoa.framework).

I just tried this as well. I added in these frameworks, but then i got
the following error:

/usr/bin/ld: warning prebinding disabled because dependent library:
/Users/hercules/Library/Frameworks/SDL.framework/Versions/A/SDL is not
prebound

I looked around and couldn’t find any references to 'hercules’
anywhere… shrug

I just took a step back and built the tests, which built and ran fine,
so I’ll just convert my apps over to pure command line until 1.2.3 comes
out.

(I’m in the process of working on a game for the 1mb game contest, as
well as my paint program (4p) hehe)

Even though i usually like command line based stuff, for some reason, i
got into doing SDL development on this thing with the Project Builder
IDE. shrug I have no qualms at all about switching back to command
line as long as it’s easy to switch back later (which it isn’t…)

-jOn Sunday, October 14, 2001, at 02:52 PM, Max Horn wrote:


Scott “Jerry” Lawrence
@Scott_Jerry_Lawrence

For all of your Cheese Weasel needs… http://www.cheeseweasel.com
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: text/enriched
Size: 1808 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20011014/9697d8e0/attachment.bin

Even though i usually like command line based stuff, for some reason, i
got into doing SDL development on this thing with the Project Builder
IDE. shrug I have no qualms at all about switching back to command
line as long as it’s easy to switch back later (which it isn’t…)

Don’t worry about it. Darrell sent new MacOS X projects this weekend,
and as soon as I finish testing them, they’ll go into the SDL CVS code.

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment

Even though i usually like command line based stuff, for some reason, i
got into doing SDL development on this thing with the Project Builder
IDE. shrug I have no qualms at all about switching back to command
line as long as it’s easy to switch back later (which it isn’t…)

Don’t worry about it. Darrell sent new MacOS X projects this weekend,
and as soon as I finish testing them, they’ll go into the SDL CVS code.

Whoot! Thanks!

:smiley:

-jOn Sunday, October 14, 2001, at 10:51 PM, Sam Lantinga wrote:


Scott “Jerry” Lawrence
@Scott_Jerry_Lawrence

For all of your Cheese Weasel needs… http://www.cheeseweasel.com

Don’t worry about it. Darrell sent new MacOS X projects this weekend,
and as soon as I finish testing them, they’ll go into the SDL CVS code.

Whoot! Thanks!

The latest CVS snapshot has the new MacOS 10.1 projects.

Unfortunately, because Apple moved the joystick headers the new snapshot
will not build on older versions of MacOS X, out of the box. Will this
be a problem for anybody?

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment

The latest CVS snapshot has the new MacOS 10.1 projects.

does SDL compile as a shared library on OSX? i thought i heard that it
only built as a “.a” static library? i’ve been trying to configure my
own library to work on OSX, but have run into some snags. it’d be great
if i could get it running though.

a big help for me would be to find all the flags needed to build a
shared lib on OSX. for example, if someone could send me the SDL_image
compile command used to build SDL_image.so, that’d be a huge help.

At 8:32 Uhr -0700 16.10.2001, Pete Shinners wrote:

The latest CVS snapshot has the new MacOS 10.1 projects.

does SDL compile as a shared library on OSX? i thought i heard that it
only built as a “.a” static library? i’ve been trying to configure my
own library to work on OSX, but have run into some snags. it’d be great
if i could get it running though.

a big help for me would be to find all the flags needed to build a
shared lib on OSX. for example, if someone could send me the SDL_image
compile command used to build SDL_image.so, that’d be a huge help.

Dynamic libs on MacOS X have a .dylib suffix :slight_smile:

And it is not a matter of sending you the right “command line”,
rather you need the right libtool version / patches for libtool.

For fink (http://fink.sourceforge.net), we use a patched version of
libtool 1.3.5 that can build proper dynamic libs on OS X, and you can
also build dynamic libs with libtool 1.4.2 (thought there are some
gotchas for the Darwin version of it :/).

Furthermore, if you build the ProjectBuilder SDL Framework - that is
automatically a shared lib.

Max–

Max Horn
Software Developer

email: mailto:Max_Horn
phone: (+49) 6151-494890