Mac OS X release

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