You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a new project with Liftoff that uses Cocoapods, the pod installation output warns that the OTHER_LDFLAGS setting has been overridden:
[!] The target `ExampleProject [Release]` overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Pods.xcconfig'.
- Use the `$(inherited)` flag, or
- Remove the build settings from the target.
[!] The target `ExampleProject [Release - Debug]` overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Pods.xcconfig'.
- Use the `$(inherited)` flag, or
- Remove the build settings from the target.
On opening the newly-generated project, I can confirm that the Other Linker Flags setting is marked as having a custom value in Build Settings - and is empty.
I would expect a fresh project to have no custom value set for this property, so that these warnings are not generated by Cocoapods. Either that, or Liftoff should add the $(inherited) flag. I'm not entirely sure whether this is a Liftoff issue, an Xcodeproj issue, a Cocoapods issue, or something else?
I can't see any mention of OTHER_LDFLAGS within the Liftoff project itself.
The text was updated successfully, but these errors were encountered:
When creating a new project with Liftoff that uses Cocoapods, the
pod
installation output warns that theOTHER_LDFLAGS
setting has been overridden:On opening the newly-generated project, I can confirm that the Other Linker Flags setting is marked as having a custom value in Build Settings - and is empty.
I would expect a fresh project to have no custom value set for this property, so that these warnings are not generated by Cocoapods. Either that, or Liftoff should add the
$(inherited)
flag. I'm not entirely sure whether this is a Liftoff issue, an Xcodeproj issue, a Cocoapods issue, or something else?I can't see any mention of
OTHER_LDFLAGS
within the Liftoff project itself.The text was updated successfully, but these errors were encountered: