Alternative to copying the SFS library to Library/Frameworks folder ?

[eyalb]

Hi,

Regarding this comment:
NOTE: in order to run an OSX application that is dependent on the SFS2X API you will need to have a copy of the library in your /Library/Frameworks/ folder. Failing to do so will cause a library loading error as soon as you hit the "Run" button.

Indeed, my project fails when I hit run.

Is there any way to overcome this? having to manually copy the library to /Library/Frameworks/ is a big issue for us.
This specific project is used only for development process, and by multiple developers, so we don't mind bundling the framework or anything like that, or any other possible solution, besides having every developer to manually do it.

Thanks!
Eyal

[mmilen]

Hi,

Here is a command to run once on your mac, change only 'full_path_to_your_library_location'.

install_name_tool -id @executable_path/../Frameworks/SFS2XAPIOSX.framework/SFS2XAPIOSX /full_path_to_your_library_location/SFS2XAPIOSX.framework/SFS2XAPIOSX

[Lapo]

Hi,

NOTE: in order to run an OSX application that is dependent on the SFS2X API you will need to have a copy of the library in your /Library/Frameworks/ folder.

Just to clarify this is a common problem with any framework for OSX, not just our API.
If you run a dedicated installer you can deploy the framework in the default OSX folder (~/Library/Frameworks). Otherwise the solution provided by mmilen is also a valid alternative.

Here's a similar discussion from the StackOverflow website:
https://stackoverflow.com/questions/162 ... xcode?rq=1

Cheers