-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Issue with framework search paths #678
Comments
Just to be clear: everything works, Xcode just warns you that the I don't think that there's really anything to be done here. The warning is annoying. Personally, I think it's ridiculous that Xcode warns you in this case without any way to silence it. But it works. There are probably a few workarounds:
Realistically, I think fixing a warning is going to be a low priority. |
It could maybe be done by adding a |
Thanks for sharing. Good to know I'm not doing something wrong at least. |
So, I'm trying this technique to resolve edwardaux/Ogra#4. The setup is as follows: my project (Ogra) embeds another project (Argo) using carthage. You can reproduce by using the following commands:
This branch contains two changes: 1) add an empty
Interestingly, through much trial and error, I found that if I remove the Argo submodule (ie. Any thoughts on what might cause the stack trace above? Thanks. |
It seems that this can be closed now: edwardaux/Ogra#4 (comment) |
I believe that comment was only referring to the error/stack trace in the previous message. I've yet to confirm if the workaround on the |
Just confirming that edwardaux/Ogra#4 (comment) was indeed only confirming that the stack trace I referenced in #678 (comment) was resolved. Not sure what the long-term solution might (if there is one?). Xcode is the guy that is emitting the spurious warning. As far as I can tell, two possible solutions are: a) the project creates the directories (this is what I was exploring for Ogra) |
I keep running into an issue where frameworks I depend on have
Carthage/Build/Mac
andCarthage/Build/iOS
in their framework search paths, which causes warnings when building my projects (I'm using the--no-build
,--use-submodules
, and--no-use-binaries
flags).Removing them is not an option for the framework author as it causes their build to fail for the project.
Some examples of this are thoughtbot/Argo#121 and edwardaux/Ogra#4.
The solution so far has been for those frameworks to add the projects of their dependencies to a workspace and use submodules.
This is how I usually deal with dependencies but I don't want to dictate how others should structure their projects if there is another way.
Is there a recommended way to solve this other than what I've described? If so, could it be added or made more prominent in the README / documentation?
The text was updated successfully, but these errors were encountered: