libvorbis

[Fx]

joevenzon - It's now ok, i had to add your adress in an accredited list in svnx (very beautifull also).

[cotharyus]

I have just commited revision 1824 - this should allow anyone out there with OS X who has been building svn versions to do so with the inclusion of all the files/frameworks needed for libvorbis. *Please* test this and let me know if it works for you. Note that you will almost certainly need the latest svn of the data repository in order for this to work.

[Fx]

i achieved also this configuration at home and it worked, effectively with an up to date data revision.

I will test your release and reports you if it's ok.

[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"

[cotharyus]

Thanks bugsyv - I'm sure the pointers will help a little as I cease floundering around and flying by the seat of my pants here, and start to move in a more guided direction - consider my progress with macs and xcode up to this point nothing short of blind luck, and educated guesses. I'm all for continuing to do it right in vdrift and make it so anyone who wants to use it, can.

[Fx]

cotharyus - Mac OS X r1824/r64 Built/linked ok I examined the way you did Frameworks integration, it is the same i validated to work on my computer libvorbis library 1.2.0 ->Good.

I tested it F1/Kyalami (the less bugged track, forget laguna seca for tests) .

We need an ogg test file now

I noticed than it's been for a while we can't ear steers weals anymore.

[cotharyus]

Good - so the Mac/Vorbis issue is basically fixed. I think last time I looked at the data directory there was a test file?

[joevenzon]

Yep, we've got an ogg test file that's some crappy original music I made a while ago. It's in there so that you can run

Code:

vdrift -test

and it makes sure it can load the file and read values.

If you want a file to play during the vdrift main menu, comment out lines 1494 to 1496 in src/game.cpp and recompile. :-)

[abs1nth]

ok i'm back from vacation now and it seems this issue is essentially fixed already - thanks to whoever added proper universal binary frameworks for ogg and vorbis to svn.

i've just commited a fix to the xcode project to actually copy those frameworks to the assembled application bundle, so the game will actually start on systems that don't have these libs installed locally.

[cotharyus]

Excellent - thank you abs1nth. I've done the best I could with what I figured out, but apparently that was the missing step. Could you elaborate a little on how you go about doing this?

[abs1nth]

the frameworks are installed by the "Copy File" build phase, visible in the "Groups & Files" pane under "Targets->vdrift->Copy Files".

(notice this is only visible if you are in the "Project" page, not in "Build" or "Debug" modes.)

i just dragged both frameworks from "vdrift->Frameworks->Linked Frameworks" to this "Copy Files" location.