• 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
is it possible to determine from a static archive file on disk which c++ compiler/linker flags were used to build it?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

is it possible to determine from a static archive file on disk which c++ compiler/linker flags were used to build it?


  • Subject: is it possible to determine from a static archive file on disk which c++ compiler/linker flags were used to build it?
  • From: Geoff Beier <email@hidden>
  • Date: Wed, 27 May 2015 11:04:58 -0400

Hi,

We're building an application that sits on top of a number of c++ libraries with different build systems that have evolved over many years. It's a little messy sometimes :)

We're currently running down a linker error on OS X introduced after one of our developers got forced into an earlier-than-planned Yosemite upgrade to accommodate new hardware. This linker error smells like one of the dependent libraries is being built with -std and -stdlib flags that do not match the others.

I'm wondering whether there's anything I can use to inspect, say, libboost_timer.a and determine what flags were used to build it. I'm specifically interested in std and stdlib. I'd like to write a script to go through all the .a files in my build tree and see whether any don't match.

Does anyone know whether I could coax this information out of otool or one of its friends?


Thanks,

Geoff
 _______________________________________________
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

  • Prev by Date: Re: Can't debug on devices
  • Next by Date: Preprocessor macros that are strings
  • Previous by thread: Re: Can't debug on devices
  • Next by thread: Preprocessor macros that are strings
  • Index(es):
    • Date
    • Thread