• 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
Per-operation, per-file arguments?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Per-operation, per-file arguments?


  • Subject: Per-operation, per-file arguments?
  • From: Rick Mann <email@hidden>
  • Date: Thu, 23 Apr 2015 17:41:23 -0700

We have some really terrible open-source code for which I've set several files to have '-Xanalyzer -analyzer-disable-checker'. Unfortunately, this applies to both Build and Analysis operations. LLVM 6.1 now warns that '-Xanalyzer -analyzer-disable-checker' is an unused argument during compilation.

Is there any way to both suppress the analyzer for this open-source code, and prevent spurious warnings when building? It's part of a separate target that builds a statically-linked library, if that helps (analysis can be turned off for the whole target).

--
Rick Mann
email@hidden



 _______________________________________________
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: Use Xcode v5.11 to debug non xcode projects
  • Next by Date: PATH for applications run inside XCode
  • Previous by thread: Re: 34 build errors magically just appeared and then Xcode 6.2 crashed.
  • Next by thread: PATH for applications run inside XCode
  • Index(es):
    • Date
    • Thread