-
Notifications
You must be signed in to change notification settings - Fork 22
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
support USE_FRAMEWORKS=static #333
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
# Conflicts: # example/ios/NitroExample.xcodeproj/project.pbxproj # example/ios/Podfile.lock
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey - thanks for your PR.
A few things;
- Watch indentation. This is not correct, I adjusted it.
- I'm not really sure if this should be in the autogenerated podspec extension. I would argue that this is something the user has to put in their podspec. Especially the FOLLY part which might change over time - Nitro does not have anything to do with Folly, this is something the user should configure in their Podspec imo.
packages/nitrogen/src/autolinking/ios/createPodspecRubyExtension.ts
Outdated
Show resolved
Hide resolved
packages/react-native-nitro-image/nitrogen/generated/ios/NitroImage+autolinking.rb
Outdated
Show resolved
Hide resolved
In my opinion, this shouldn't go in the This should go into |
That's right, I'll reference other libraries instead of editing autolink.
|
Hey @mrousavy,
Second, I don't find any ways to support build static so I will edit podspec to support GCC_PREPROCESSOR_DEFINITIONS
Hope we can use this solution for USE_FRAMEWORKS=static |
Fix issue: #219 #218