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

Fix ShipIt dependency linking. #236

Closed

Conversation

devinfoley
Copy link
Contributor

A recent change to Squirrel attempted to link to ReactiveCocoa and Mantle in ShipIt, vs copying and compiling their source files into the ShipIt binary. This was done because, in certain environments, dylib was loading multiple copies of the classes, which was causing errors in ReactiveCocoa's assertions.

This PR actually removes the dependency classes from the Copy Files build step. It adds an additional build step to re-link ReactiveCocoa and Mantle, using @executable_path instead of @rpath, as @rpath linking was causing the same double loading problem in certain environments.

@Neoster
Copy link

Neoster commented Jul 3, 2019

When will this be merged? I think it will fix my issues i am having using Squirrel....

@devinfoley
Copy link
Contributor Author

Closing because this is covered by #242

@devinfoley devinfoley closed this Jul 16, 2020
@devinfoley devinfoley deleted the explicit_linking_shipit branch July 16, 2020 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants