-
Notifications
You must be signed in to change notification settings - Fork 467
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
Different module names in Carthage and Cocoapods #411
Comments
I don't have experience with Carthage but I don't think this is related to migration (unless I made mistake at some point). I think it might be just question of renaming If you know how to fix it I am happy to accept PR. |
Actually renaming |
I tried to rename the |
I am trying now and it seems ok. Have you renamed it in all 3 targets? |
Merged, thanks for that. Do you need separate release for this? |
@jcavar thanks!
do you maybe have a clue what might be causing this? |
probably I had to update the headers in Build Phases as well! - testing that now, will update my PR |
Yeah I think |
I removed the MQTTFramework.h |
It could be. |
We are building an iOS framework that includes MQTT-Client-Framework as a dependency. We plan to support both CocoaPods and Carthage for our developers. We have started with Pods, all compiles well but when building the Carthage target we have noticed that we can't include MQTTClient module anymore - it's called 'MQTTFramework' there.
Works only with CocoaPods:
import MQTTClient
Works only with Carthage:
import MQTTFramework
The problem is that we can't use the same codebase for both Carthage and Pods targets.
I understand it might be related to the ckrey -> novastone migration?
If the naming unification is planned for later, can anyone suggest a temporary solution how i could fix it in our project?
The text was updated successfully, but these errors were encountered: