-
Notifications
You must be signed in to change notification settings - Fork 185
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
Is it possible to use the Pod without use_frameworks!
?
#237
Comments
use_frameworks!
?use_frameworks!
?
I'm also working on a React Native app and was having problems with I did this by:
plugin 'cocoapods-user-defined-build-types'`
enable_user_defined_build_types! right after the second At this point, once I tried building the project, I was getting errors about |
@flash76 I got back to this problem and your solution works, thanks a lot! I am working on a react-native application with Flipper, which does not work with There are also several workarounds, e.g.. having selected libraries marked as static, but it runs into a problems if any of selected Flipper deps are also transitive dependencies of other dependencies and are expected to be built as frameworks. So thanks for this! Reversed approach having only selected pods built as Frameworks works much better! |
I have a Cocoapod project that for some reason does not use
use_frameworks!
directive (legacy, react-native had issues with the frameworks).Compilation fails with linking errors for Sodium 0.9.1.
I was wondering whether it is possible to use this Sodium pod without using
use_frameworks!
or using the framework is a fundamental requirement for the Sodium pod.It is easy to reproduce with
pod spec lint
on this repository:The following Lint passes:
The following does not. The error is the same as when I am using Sodium in my project.
I've created a simple demo project depending on Sodium 0.9.1: https://github.com/ph4r05/SodiumPoc
When
use_frameworks!
is present in https://github.com/ph4r05/SodiumPoc/blob/main/Example/Podfile it builds, otherwise not.use_frameworks! :linkage => :static
use_modular_headers!
alone does not workThe text was updated successfully, but these errors were encountered: