Version 1.0.2 iOS: 138 Dsymutil warnings

[Pascal]

I updated the Couchbase framework in our iOS app to version 1.0.2 and now I'm receiving 138 Dsymutil warnings when compiling. They all look like this:

(null): warning: (x86_64) /Users/jenkins/jenkins/workspace/build_cblite_ios_102-enterprise/couchbase-lite-ios/build/CouchbaseLite.build/Release-iphonesimulator/CBL iOS library.build/Objects-normal/x86_64/CBLChangeTracker_Tests.o unable to open object file

Any ideas on how to make them go away?

[Jens Alfke]

On Sep 7, 2014, at 7:07 AM, Pascal <phase.o...@gmail.com> wrote:

(null): warning: (x86_64) /Users/jenkins/jenkins/workspace/build_cblite_ios_102-enterprise/couchbase-lite-ios/build/CouchbaseLite.build/Release-iphonesimulator/CBL iOS library.build/Objects-normal/x86_64/CBLChangeTracker_Tests.o unable to open object file

A number of people have already reported this here — apparently the fix is to change your app target's debugging symbols build setting.

(I've been meaning to investigate why this happens, but I have to confess that messing with Xcode library build settings becomes so frustrating that I can only approach it in limited doses.)

—Jens

[Pascal]

I couldn't agree more on Xcode's build-a-library handling. Unfortunately however the suggested fix (turning off dSYM generation) is incompatible with Crashlytics: apps using Crashlytics will refuse to build if dSYM is turned off.

[Andrew Tetlaw]

We only change it for Debug only and we disable Crashlytics for Debug too

[Pascal]

That could work for me too, I had Crashlytics on for Debug on device to to get reports when I test on the road and it crashes. It's still quite scary to receive 138 warnings when archiving the app for a submission build.

[Phil Mitchell]

Jens, It looks like the fix is to set GCC_GENERATE_DEBUGGING_SYMBOLS = NO in Build Settings. In XCode 6, you do this by going to:

   Build Settings (All) => Apple LLVM 6.0 - Code Generation

and setting "Generate Debug Symbols" to NO for your release build.

I don't mean to be a pain, but I don't think it makes sense for consumers of the framework to do this -- we need those symbols. But these warnings are a hassle and it would be great if you guys could turn them off.

http://stackoverflow.com/questions/14489692/what-do-these-dsymutil-warnings-mean-in-xcode-4-5

Thanks!

[Jens Alfke]

On Oct 24, 2014, at 6:14 PM, Phil Mitchell <seasp...@gmail.com> wrote:

I don't mean to be a pain, but I don't think it makes sense for consumers of the framework to do this -- we need those symbols. But these warnings are a hassle and it would be great if you guys could turn them off.

There isn't a real fix for this, due to limitations of the linker. The only thing we could do would be to back out the change that made this happen. But the purpose of that change was to hide internal symbols — before, people were having trouble building apps that happen to use some of the same libraries (like yajl) that CBL does, because the linker would complain about duplicate symbols. As it stands, linker warnings are less bad than linker errors :(

—Jens