libvorbis

[bugsyv]

Ok. You'll have to break that framework bundle thing down for me a little. I think I understand what you're talking about, but not sure I understand how to do it, based on what I've seen so far. Part of being new to the world of mac and mac development.

I suspected the dylibs thing was probly something like that. Since both libvorbis and libogg were built from source from the command line, I'm assuming there's some switch I have to throw to make the libs work for universal builds - but I haven't had time to sort out what it is yet. Pointers?

I haven't access to my mac right now, so I can't give a ton of details... and your most recent post indicates you have handled this alright anyhow.

Anyways.. in mac land, a bundle is a package of stuff... you can have an app bundle or a framework bundle or plugin or maybe other stuff. It is basically jsut a specially arrange directory structure with some meta data in certain files ( Info.plist ). A framework bundle usually contains dylibs and include headers... and most OSS projects that I have bothered with do not seem to create these by default. I have no idea how abs1nt ( or someone else ) has been creating these. For examples see tools/osx/SDL.framework and friends.

For more detailed information, search the xcode docs for "carbon bundle"