-
Notifications
You must be signed in to change notification settings - Fork 466
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
the 'xcodeproj' argument doesn't respect SWIFT_OPTIMIZATION_LEVEL flags #354
Comments
I'm using cocopods 0.39, and Xcode 7.2 |
In debug on master it seems to be set to |
If they're not set, they'll use the default. Same as when you create a new framework via the Xcode new target menu. |
OK, here's a video of what I'm doing. It's 5 minutes long, unedited. I do the following:
End result is while the config named "Debug" does have Swift optimizations turned to "none", QA & DEV do not (although the do in the LLVM). |
Issue stems from
|
exact copy of this issue: CocoaPods/CocoaPods#4867
I'm having trouble using the "xcodeproj" (soon to be "project") argument in my Podfile.
I'm using the "xcodeproj" argument to describe which configurations should be treated as "debug" and which should be treated as "release" like this:
xcodeproj 'SpecialProj', 'DEV' => :debug, 'QA' => :debug, 'PROD' => :release
While this flag does set the optimization levels correctly for Apple LLVM 7.0, it does not do something similar for the Swift compiler. Shouldn't it?
The text was updated successfully, but these errors were encountered: