• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Linker warnings incorporating debug symbols from prelinked static library
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linker warnings incorporating debug symbols from prelinked static library


  • Subject: Linker warnings incorporating debug symbols from prelinked static library
  • From: Jens Alfke <email@hidden>
  • Date: Fri, 19 Sep 2014 10:38:02 -0700

In my day job I develop a framework (Couchbase Lite) that's shipped as a static library for iOS.
In the latest release, I changed the build process: enabling "single object prelink", making symbols private by default, and using an exported-symbols file so that only the symbols in the public API are visible.

The problem is that developers are now reporting that when they build their apps that import this library, they get 160 linker warnings of the form:

warning: (arm64) /Users/jenkins/jenkins/workspace/build_cblite_ios_102-community/couchbase-lite-ios/build/CouchbaseLite.build/Release-iphoneos/CBL iOS library.build/Objects-normal/arm64/CBL_Revision.o unable to open object file

(CBL_Revision.o is the object code of a source file in the library, and the long path is apparently where it's located when our automated build server builds the library. There's one of these warnings for each object file from the library.)

Developers have reported that the warnings can be suppressed by changing their applications' Build Setting Debug Information Format from "DWARF with dSYM file" to "DWARF". But this isn't a perfect workaround, because doing so makes the app incompatible with the popular Crashlytics service.

I've tried changing the library target between DWARF and DWARF-with-dSYM, and changing the symbol-stripping options to not strip debug symbols, but it doesn't make any difference.

Anyone know how to resolve this? To be specific:
* This is an iOS static library, to be linked into 3rd party apps.
* The apps should incorporate sufficient debug symbols from the library so that library method names will show up in backtraces, crash reports, etc.
* And there shouldn't be hundreds of link warnings :)

—Jens
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Linker warnings incorporating debug symbols from prelinked static library
      • From: email@hidden
  • Prev by Date: Re: FYI: docs are working again in Xcode 5.
  • Next by Date: Re: Linker warnings incorporating debug symbols from prelinked static library
  • Previous by thread: Re: FYI: docs are working again in Xcode 5.
  • Next by thread: Re: Linker warnings incorporating debug symbols from prelinked static library
  • Index(es):
    • Date
    • Thread