Hey there! After installing AudioKit 4.1 using CocoaPods (pod 'AudioKit') in Xcode 9.2, I get 27 build errors under Dsymutil Warning. Seems it's due to some settings of the built static framework.
GenerateDSYMFile /Users/Account/Library/Developer/Xcode/DerivedData/AppName-evpgbjtnaccxkydwomsoaswnluct/Build/Products/Debug-iphonesimulator/AppName.app.dSYM /Users/Account/Library/Developer/Xcode/DerivedData/AppName-evpgbjtnaccxkydwomsoaswnluct/Build/Products/Debug-iphonesimulator/AppName.app/AppName
cd "/Users/Account/Dropbox/Developer/appname"
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil /Users/Account/Library/Developer/Xcode/DerivedData/AppName-evpgbjtnaccxkydwomsoaswnluct/Build/Products/Debug-iphonesimulator/AppName.app/AppName -o /Users/Account/Library/Developer/Xcode/DerivedData/AppName-evpgbjtnaccxkydwomsoaswnluct/Build/Products/Debug-iphonesimulator/AppName.app.dSYM
while processing /Users/Account/Dropbox/Developer/appname/Pods/AudioKit/iOS/AudioKit.framework/AudioKit(t.o):
warning: /var/folders/g3/3gw8_98n3d7_qkzthq9tx6t00000gn/C/org.llvm.clang.megastep/ModuleCache/28QYBKEQP3153/Darwin-38I6DLZ5IH61J.pcm: No such file or directory
note: Linking a static library that was built with -gmodules, but the module cache was not found. Redistributable static libraries should never be built with module debugging enabled. The debug experience will be degraded due to incomplete debug information.
Yeah, I noticed that too and updated the build settings for the AudioKit frameworks. It should take effect in the next release (4.1.1 or 4.2, depending) - but in the meantime you can just ignore these warnings if you want to keep using the precompiled binary that the pod fetches.
I'm still seeing these warnings in Xcode 9.3 on AudioKit 4.2.3 @megastep
Most helpful comment
Yeah, I noticed that too and updated the build settings for the AudioKit frameworks. It should take effect in the next release (4.1.1 or 4.2, depending) - but in the meantime you can just ignore these warnings if you want to keep using the precompiled binary that the pod fetches.