Using static libraries with CocoaPods 1.5 no such module at import
With CocoaPods 1.5 released I am trying to migrate from having 10-15 dynamic pods in my projects to having them as static libraries instead, with the goal of speeding up my app start time.
At this stage my simple (i.e., simplistic) attempt has been to remove the use_frameworks command when running my pod install. This indeed transforms my pods to static libraries. But it also produces a series of "No Such Module" throughout my project when trying to import my Pods (e.g., "No such Module PureLayout or no such Module FirebaseMessaging).
I am not super versed in all the intricacies of pods and dynamic/ static libraries and have tried for the past day to find good documentation on how to properly import, use and deploy static libraries for a Swift Project but could not find clear guidelines.
I am using XCode 10.1 and CocoaPod 1.5.2 (client version).
Could anyone help me by providing links to detailed instructions on how to move from dynamic to static libraries?
Thanks a ton!
ios swift cocoapods static-libraries
asked Nov 12 at 15:01
Franc
133
add a comment |
With CocoaPods 1.5 released I am trying to migrate from having 10-15 dynamic pods in my projects to having them as static libraries instead, with the goal of speeding up my app start time.
At this stage my simple (i.e., simplistic) attempt has been to remove the use_frameworks command when running my pod install. This indeed transforms my pods to static libraries. But it also produces a series of "No Such Module" throughout my project when trying to import my Pods (e.g., "No such Module PureLayout or no such Module FirebaseMessaging).
I am not super versed in all the intricacies of pods and dynamic/ static libraries and have tried for the past day to find good documentation on how to properly import, use and deploy static libraries for a Swift Project but could not find clear guidelines.
I am using XCode 10.1 and CocoaPod 1.5.2 (client version).
Could anyone help me by providing links to detailed instructions on how to move from dynamic to static libraries?
Thanks a ton!
ios swift cocoapods static-libraries
asked Nov 12 at 15:01
Franc
133
add a comment |
With CocoaPods 1.5 released I am trying to migrate from having 10-15 dynamic pods in my projects to having them as static libraries instead, with the goal of speeding up my app start time.
At this stage my simple (i.e., simplistic) attempt has been to remove the use_frameworks command when running my pod install. This indeed transforms my pods to static libraries. But it also produces a series of "No Such Module" throughout my project when trying to import my Pods (e.g., "No such Module PureLayout or no such Module FirebaseMessaging).
I am not super versed in all the intricacies of pods and dynamic/ static libraries and have tried for the past day to find good documentation on how to properly import, use and deploy static libraries for a Swift Project but could not find clear guidelines.
I am using XCode 10.1 and CocoaPod 1.5.2 (client version).
Could anyone help me by providing links to detailed instructions on how to move from dynamic to static libraries?
Thanks a ton!
ios swift cocoapods static-libraries
asked Nov 12 at 15:01
Franc
133
With CocoaPods 1.5 released I am trying to migrate from having 10-15 dynamic pods in my projects to having them as static libraries instead, with the goal of speeding up my app start time.
At this stage my simple (i.e., simplistic) attempt has been to remove the use_frameworks command when running my pod install. This indeed transforms my pods to static libraries. But it also produces a series of "No Such Module" throughout my project when trying to import my Pods (e.g., "No such Module PureLayout or no such Module FirebaseMessaging).
I am not super versed in all the intricacies of pods and dynamic/ static libraries and have tried for the past day to find good documentation on how to properly import, use and deploy static libraries for a Swift Project but could not find clear guidelines.
I am using XCode 10.1 and CocoaPod 1.5.2 (client version).
Could anyone help me by providing links to detailed instructions on how to move from dynamic to static libraries?
Thanks a ton!
ios swift cocoapods static-libraries
ios swift cocoapods static-libraries
asked Nov 12 at 15:01
Franc
133
asked Nov 12 at 15:01
Franc
133
asked Nov 12 at 15:01
Franc
133
asked Nov 12 at 15:01
Franc
133
asked Nov 12 at 15:01
Franc
133
133
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
CocoaPods 1.5.0 introduced use_modular_headers! to still provide module support with static libraries. Details in the release notes.
Alternatively you could change the modular imports in your sources to file imports.
I'd also recommend trying out the CocoaPods 1.6.0 beta since it has several fixes for static/dynamic library and framework issues.
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
It works! I don't understand why but it did the trick :) What are the modular headers for and why not including them prevented my app to compile my pods?
– Franc
Nov 14 at 3:27
CocoaPods does not generate modules for static libraries unlessuse_modular_headers!is specified.
– Paul Beusterien
Nov 14 at 5:11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264846%2fusing-static-libraries-with-cocoapods-1-5-no-such-module-at-import%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
CocoaPods 1.5.0 introduced use_modular_headers! to still provide module support with static libraries. Details in the release notes.
Alternatively you could change the modular imports in your sources to file imports.
I'd also recommend trying out the CocoaPods 1.6.0 beta since it has several fixes for static/dynamic library and framework issues.
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
It works! I don't understand why but it did the trick :) What are the modular headers for and why not including them prevented my app to compile my pods?
– Franc
Nov 14 at 3:27
CocoaPods does not generate modules for static libraries unlessuse_modular_headers!is specified.
– Paul Beusterien
Nov 14 at 5:11
add a comment |
CocoaPods 1.5.0 introduced use_modular_headers! to still provide module support with static libraries. Details in the release notes.
Alternatively you could change the modular imports in your sources to file imports.
I'd also recommend trying out the CocoaPods 1.6.0 beta since it has several fixes for static/dynamic library and framework issues.
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
It works! I don't understand why but it did the trick :) What are the modular headers for and why not including them prevented my app to compile my pods?
– Franc
Nov 14 at 3:27
CocoaPods does not generate modules for static libraries unlessuse_modular_headers!is specified.
– Paul Beusterien
Nov 14 at 5:11
add a comment |
CocoaPods 1.5.0 introduced use_modular_headers! to still provide module support with static libraries. Details in the release notes.
Alternatively you could change the modular imports in your sources to file imports.
I'd also recommend trying out the CocoaPods 1.6.0 beta since it has several fixes for static/dynamic library and framework issues.
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
CocoaPods 1.5.0 introduced use_modular_headers! to still provide module support with static libraries. Details in the release notes.
Alternatively you could change the modular imports in your sources to file imports.
I'd also recommend trying out the CocoaPods 1.6.0 beta since it has several fixes for static/dynamic library and framework issues.
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
answered Nov 12 at 16:03
Paul Beusterien
13.6k43579
13.6k43579
It works! I don't understand why but it did the trick :) What are the modular headers for and why not including them prevented my app to compile my pods?
– Franc
Nov 14 at 3:27
CocoaPods does not generate modules for static libraries unlessuse_modular_headers!is specified.
– Paul Beusterien
Nov 14 at 5:11
add a comment |
It works! I don't understand why but it did the trick :) What are the modular headers for and why not including them prevented my app to compile my pods?
– Franc
Nov 14 at 3:27
CocoaPods does not generate modules for static libraries unlessuse_modular_headers!is specified.
– Paul Beusterien
Nov 14 at 5:11
It works! I don't understand why but it did the trick :) What are the modular headers for and why not including them prevented my app to compile my pods?
– Franc
Nov 14 at 3:27
It works! I don't understand why but it did the trick :) What are the modular headers for and why not including them prevented my app to compile my pods?
– Franc
Nov 14 at 3:27
CocoaPods does not generate modules for static libraries unless
use_modular_headers! is specified.– Paul Beusterien
Nov 14 at 5:11
CocoaPods does not generate modules for static libraries unless
use_modular_headers! is specified.– Paul Beusterien
Nov 14 at 5:11
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264846%2fusing-static-libraries-with-cocoapods-1-5-no-such-module-at-import%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
