-
Notifications
You must be signed in to change notification settings - Fork 174
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
Should not list Carthage in Framework Search Paths #25
Comments
Do we agree that this should/can be fixed? It's our last warning in our codebase currently. |
Oh sorry, I totally forgot about it. 🙏 Could you please create a PR for this? I'm not experienced with Carthage. |
Sure, I'll try to get to it this week. |
@freak4pc You need to build the project by including it in the workspace, not buy using |
Could you provide a dummy project? I'm not sure which workspace you're referring to in that case :) |
In the image you have, you have To provide an example project I would probably spend the couple more minutes and fix it, so it would be on the same timeline, sometime this week. Carthage itself uses this format though (https://github.com/Carthage/Carthage/blob/master/Carthage.xcworkspace/contents.xcworkspacedata) so you can see how they setup their workspace for an example. |
Ok, not sure if I'm doing anything special here but - I did reproduce your issue, when dragging the product framework from RxKeyboard to my own project in the same workspace, it showed that message, but then I noticed that "Framework Search Path" was configured on my own project and not on RxKeyboard. When removing that line, I'm not seeing that warning again. Anyways if you're still experiencing it I'll leave it to you since I can't find an issue inside RxKeyboard itself :) |
Currently
FRAMEWORK_SEARCH_PATHS
is set to$(PROJECT_DIR)/Carthage/Build/iOS
. This gives a warning when building from source in a consuming workspace:The correct setup is to not have this and to include RxSwift in the Workspace and use Xcode's Implicit Dependency Management. That way it knows how to compile both as a part of Carthage and in the workspace for development: https://www.quora.com/How-should-an-OSS-library-be-structured-for-distribution-with-both-Carthage-and-CocoaPods/answer/Justin-Spahr-Summers
The text was updated successfully, but these errors were encountered: