Comments on: SeattleBus Diary: Using CLANG static analyzer with an iPhone project

By: Joe

Joe — Tue, 08 Mar 2011 17:03:31 +0000

It means you don’t have your keys set up for code signing. Go to https://developer.apple.com/ios/manage/overview/, log in with your ADC account, and there’s both instructions and a wizard to help you get that all set up.

By: Pradeep

Pradeep — Tue, 08 Mar 2011 04:32:01 +0000

Check dependencies
Code Sign error: The identity ‘iPhone Developer’ doesn’t match any valid certificate/private key pair in the default keychain
[BEROR]Code Sign error: The identity ‘iPhone Developer’ doesn’t match any valid certificate/private key pair in the default keychain
** BUILD FAILED **
- I got this error, what does it mean.

By: Joe

Joe — Fri, 12 Jun 2009 05:30:43 +0000

You should still be able to get Clang open source to function with the current SDK (gcc 4.2). However, I suspect that if you wait until September, the workarounds to get the open source project will be mitigated.

By: tommy

tommy — Fri, 12 Jun 2009 01:30:32 +0000

It seem that it does not work for sdk 3.0 wrong gcc

By: lionstarr

lionstarr — Mon, 04 May 2009 18:11:07 +0000

Hi!
I am trying to get this running. I made sure, that all the steps you suggested are done and I did a xcodebuild clean before running scan-build. Unfortunately, this runs and displays a webpage, which only describes errors related to compiling: Namely: “-miphoneos-version-min=2.2.1 is invalid, expected something like ’2.0′.”.
Any Idea, what I can do to make this work for me? I really need help finding my leaks

By: Image memory at Under The Bridge

Image memory at Under The Bridge — Sat, 03 Jan 2009 04:11:41 +0000

[...] for device builds no … but the simulator uses Intel binaries! Convenient, no? Thanks to this post for explaining to us My workflow after I’ve really worked on the codebase is [...]

By: David

David — Mon, 17 Nov 2008 18:34:13 +0000

Thanks for this! I ran scan-build on my project, but after going after the “low hanging fruit”, I had problems running it again. I would get some build errors that didn’t come with much explanation (and things built just fine with xCode). After running those “rm” commands, it worked great!