Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support @loader_path and @rpath #2

Open
ronaldoussoren opened this issue Mar 13, 2011 · 2 comments
Open

Support @loader_path and @rpath #2

ronaldoussoren opened this issue Mar 13, 2011 · 2 comments
Labels
enhancement New feature or request major

Comments

@ronaldoussoren
Copy link
Owner

Original report by Ronald Oussoren (Bitbucket: ronaldoussoren, GitHub: ronaldoussoren).


Since at least OSX 10.5 dyld has supported the @loader_path and @rpath special prefixes for the installed name in library dependencies.

Macholib needs to support those in rewrites and while looking for libraries (macholib.dyld)

@ronaldoussoren
Copy link
Owner Author

Original comment by Anonymous.


Hi Ronald,

Has there been any progress on this issue? Or is there a recommended workaround to switch the @executable_path references to @loader_path? I'm using py2app to build a plugin, which breaks when imported into Xcode since the @executable_path differs when referring to frameworks used by the plugin. I would very much appreciate support for this.

Thanks for your hard work on py2app!

Shravan

@ronaldoussoren
Copy link
Owner Author

Original comment by Ronald Oussoren (Bitbucket: ronaldoussoren, GitHub: ronaldoussoren).


py2apps now mostly works with shared libraries that use @loader_path, this will be in the next release.

Changing py2app to use @loader_path instead of @executable_path would be a lot more work, this may or may not happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request major
Projects
None yet
Development

No branches or pull requests

1 participant