Mac OS X release

[abs1nth]

hello againi'm 100% sure i've already replied to your post, but either the forum ate my post or i missed the "Submit" button ;o)here we go again:

Well, now I can compile the files BUT it doesn't link.... :cry: I have the following errors"/usr/bin/ld: table of contents for archive: /Volumes/Documents/vdrift_580/tools/osx/libfmod.a is out of date; rerun ranlib(1) (can't load from it)"How can I rerun ranlib and what is it ???

i've discovered this error too, when i was trying to reproduce your problems...(dunno what caused it since libfmod.a was always working...)...i've (hopefully) fixed it and if you do a "svn update" it should work for you alternatively you could open Terminal.app, type "ranlib /Path/to/libfmod.a" hit enter and it should work too..

and "/usr/bin/ld: warning prebinding disabled because dependent library: /Developer/SDKs/MacOSX10.3.9.sdk/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit can't be searched"Why the Mac OS X 10.3.9 SDK is used and not the Mac OS X 10.4 SDK ? (Maybe this is a stupid question)

using the 10.3.9 SDK ensures the vdrift will also run under 10.3.x and not only 10.4.x where is is beeing built...don't know why you get this warning...are you sure you habe the 10.3.9 SDK installed?

Definitively, even if I don't know many things about Mac OS X development, I feel frustrated not being able to compile the project just by clicking on the build icon. I strongly believe a FAQ or readme file is necessary explaining how to compile successfully the project on Mac OS X.What's your feeling ?

my feeling is if the project does not compile "just by clicking on the build icon" that is an bug that should be fixed instead of providing workarounds in a FAQ. (the problem here of course is that at the time an release is made the sources my countain mac-specific bugs, and the version in svn is never guaranteed to work...)

[christophe14]

Hello,

i've discovered this error too, when i was trying to reproduce your problems...(dunno what caused it since libfmod.a was always working...)...i've (hopefully) fixed it and if you do a "svn update" it should work for you alternatively you could open Terminal.app, type "ranlib /Path/to/libfmod.a" hit enter and it should work too..

I have good news with the version 620. Now I can link both targets Development and Deployment !But not the Deployment-Release. I have got the following errors:" mkdir /Volumes/Documents/vdrift_620/tools/osx/build/Deployment-Release/vdrift.app/Contents (error: Too many levels of symbolic links) cd /Volumes/Documents/vdrift_620/tools/osx /System/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -strip-debug-symbols -resolve-src-symlinks /Volumes/Documents/vdrift_620/tools/osx/build/vdrift.build/Deployment-Release/vdrift.build/Info.plist /Volumes/Documents/vdrift_620/tools/osx/build/Deployment-Release/vdrift.app/Contentserror: couldn't create directory /Volumes/Documents/vdrift_620/tools/osx/build/Deployment-Release/vdrift.app/Contents: Too many levels of symbolic linkspbxcp: error: open(): /Volumes/Documents/vdrift_620/tools/osx/build/Deployment-Release/vdrift.app/Contents/Info.plist [/SourceCache/pbx_tools/pbx_tools-628.1/pbxcp/file_utils.c:391]: Too many levels of symbolic links"

using the 10.3.9 SDK ensures the vdrift will also run under 10.3.x and not only 10.4.x where is is beeing built...don't know why you get this warning...are you sure you habe the 10.3.9 SDK installed?

I have 10.2.8, 10.3.9 and 10.4 SDK installed with Xcode. Anyway with the new project, this warning has disappeared.

my feeling is if the project does not compile "just by clicking on the build icon" that is an bug that should be fixed instead of providing workarounds in a FAQ. (the problem here of course is that at the time an release is made the sources my countain mac-specific bugs, and the version in svn is never guaranteed to work...)

That's exactly what I wanted to hear. :lol: This means the ReadMe.rtf should contain information about Simple DirectMedia Layer: - where to find them (URL)- how to install themThis last point is very important.This is what I have found:The file "SDL_image.h" is installed in "SDL_image.framework" and not in "SDL.framework".Same thing concerning the file "SDL_net.h" present in "SDL_net.framework" and not "SDL.framework".This leads to many errors in different header files while compiling.So I have moved all the files contained both in "SDL_image.framework" and "SDL_net.framework" into "SDL.framework". Then I have found another error while linking: if I remember correctly, the project is looking for the file SDL_net in the "SDL_net.framework"...Have you faced these problems ?

[abs1nth]

Hello,I have good news with the version 620. Now I can link both targets Development and Deployment !

great :lol: This means the ReadMe.rtf should contain information about Simple DirectMedia Layer: - where to find them (URL)- how to install them[/QUOTE]well the readme is a readme for the binary distibution and not for the developers. i didn't want to clutter it up or create a new file since i thought 99.9% of mac users wouldn't build from source anyway ^^ maybe i was wrong

This last point is very important.This is what I have found:The file "SDL_image.h" is installed in "SDL_image.framework" and not in "SDL.framework".Same thing concerning the file "SDL_net.h" present in "SDL_net.framework" and not "SDL.framework".This leads to many errors in different header files while compiling.So I have moved all the files contained both in "SDL_image.framework" and "SDL_net.framework" into "SDL.framework".

hm the problem is all those "#include " in the code base expect the standard unix set-up of the sdl headers in "/usr/local/include/SDL/" and not the macosx-special framework setup. it wasn't a problem for me since i have the sdl libraries/headers installed in unix as well in framework way (for building all those command-line sdl projects). ^^ maybe it is just easier to require that mac developers have SDL* installed in both ways instead of uglifying all the code with conditionals for OSX

Then I have found another error while linking: if I remember correctly, the project is looking for the file SDL_net in the "SDL_net.framework"...Have you faced these problems ?

yes i recall that some of the SDL_* framework packages for osx had a completely broken layout...i fixed them manually....there is nothing we can do about this besides bugging the SDL_* maintainers to release fixed packages....

[christophe14]

weird. good news is you shouldn't need this target anyway since it is used to create the deployable .dmg files for distribution ^^your error may go away if you choose "edit project settings" from the "project" menu in xcode and choose a custom build location...maybe an empty folder on the root of your hd?

I have tried to copy the project on the root, to change the build location, to reduce the path length to the minimum.. But I still didn't succeed..."error: couldn't create directory /Release/vdrift.app/Contents: Too many levels of symbolic links"

well the readme is a readme for the binary distibution and not for the developers. i didn't want to clutter it up or create a new file since i thought 99.9% of mac users wouldn't build from source anyway ^^ maybe i was wrong

As long as the vdrift-2005-xx-xx-src.tar.bz2 archive file will contain a Mac OS X project, any indication explaining how to compile should be added. (I cannot forget 6 years of customer support )

[thelusiv]

I agree, it would be nice to have some instructions on how to compile VDrift for OS X, so we could put them in the FAQ manager on this site. There are similar instructions for Linux, and they need to be updated for Windows and FreeBSD as well.The documentation that comes with the game is generated dynamically from the FAQ, so that is the best place to put the instructions. Only certain users have access to the FAQ, and I have to give out rights and explain it to them...I have been wondering if perhaps it's worth setting up a wiki on the site to help manage documentation. It might be easier that way to write and update it. We need some more documentation on the different configuration text files and how to change them...this would make it a little easier for people to develop new cars & tracks, or otherwise modify the game.

[abs1nth]

ok so it would if i was notified in advance of an release so i can ensure the mac-specific stuff works fine...i will take care of the compile instructions...about the error with the symblolic links ... i have no clue why it works for me and not for you but i will have a look

[joevenzon]

Because a lot of the new features being worked on at the moment are large changes, the next release will be a big one (and maybe a long time coming), so we'll let you know ahead of time. Hopefully we can do some internal testing before doing a public release.

[christophe14]

i will take care of the compile instructions...

What do you think of the following text:The VDrift Mac OS X project requires Xcode version 2.2 with Mac OS X 10.3.9 SDK installed.Before compiling VDrift, the complete Simple DirectMedia Layer library has to be installed:- SDL network (http://www.libsdl.org/projects/SDL_net/r...pkg.tar.gz)- SDL image (http://www.libsdl.org/projects/SDL_image...pkg.tar.gz)- SDL runtime (http://www.libsdl.org/release/SDL-1.2.9.dmg)- SDL development (http://www.libsdl.org/release/SDL-devel-...ar.gz)Then copy the following files:- SDL_image.h from /Library/Frameworks/SDL_image.framework/Versions/A/Headers to /Library/Frameworks/SDL.framework/Versions/A/Headers- SDL_net.h from /Library/Frameworks/SDLnet.framework/Versions/A/Headers to /Library/Frameworks/SDL.framework/Versions/A/HeadersDo not remove the directories named SDL_image.framework and SDL_net.framework !Then compile and enjoy... :wink:

about the error with the symblolic links ... i have no clue why it works for me and not for you but i will have a look

Thanks for your continuous support !

[abs1nth]

What do you think of the following text:

thanks! i've modified it a bit and updated the faq page at:http://vdrift.net/faqman/index.php?op=view&t=31(i know that the formatting is sub-optimal...)i will also commit an updated ReadMe.rtf soonbtw. i don't like the instructions about copying some of the sdl header files since it is NOT the proper solution, but oh-well ^^ it's fine it it works i guess :wink:

So we'll let you know ahead of time

great!

[christophe14]

[quote="abs1nth"] thanks! i've modified it a bit and updated the faq page at:http://vdrift.net/faqman/index.php?op=view&t=31(i know that the formatting is sub-optimal...)i will also commit an updated ReadMe.rtf soonbtw. i don't like the instructions about copying some of the sdl header files since it is NOT the proper solution, but oh-well ^^ it's fine it it works i guess :lol:

[christophe14]

about the error with the symblolic links ... i have no clue why it works for me and not for you but i will have a look

Will it be possible for you to give me the path of your project so that I can make a test ? I mean the complete path of your Xcode project versus the src directory (including the name of your hard disk) ...Thanks

[abs1nth]

about the error with the symblolic links ... i have no clue why it works for me and not for you but i will have a look

Will it be possible for you to give me the path of your project so that I can make a test ? I mean the complete path of your Xcode project versus the src directory (including the name of your hard disk) ...Thanks

i've told XCode to place ALL build products and intermediate files in "/Users/julian/Documents/Development/_BUILD":trough XCode -> Preferences -> Building: Place Build Products in: Customized Location: "/Users/julian/Documents/Development/_BUILD" Place Intermediate Build Files in: With build productsso the path of the actual vdrift shouldn't matter but i normally build it right from my desktop "/Users/julian/Desktop/vdrift"