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
Carthage support #230
Comments
I think I noticed yesterday that our unit test bundles don't have the run path search paths configured properly, but I haven't had time to confirm. They should look like this (you should be able to copy/paste this into the settings editor):
Let me know if that helps, and we can work on adding a fix. |
@gfontenot I'll take a look when I get a chance and let you know. Thanks |
Forgot to write back...sorry. Unfortunately that didn't work @gfontenot |
I'll need more info on what the failure is. |
@gfontenot I apologize, forgot to follow up. Looks like dragging frameworks built by carthage didn't also add the path to |
Ah, good to hear. Sorry you were having problems. |
I'm having trouble tracking this down but seems to be that I cannot build a project initialized and started by liftoff with carthage frameworks. That is to say that libraries linked through carthage instead of cocoa pods seem to result in the invocation error. Any word on this? I didn't see anyone else having issues with it but did see an issue for documenting carthage support.
The text was updated successfully, but these errors were encountered: