Since there is no Xcode script variable for "current project directory," how can you create a script menu item to run the Clang Static Analyzer on your current project from Xcode?
+3
A:
From the XCode script menu item, "Edit User Scripts" enter the following script:
#!/bin/bash
result=$( osascript << END
tell application "Xcode"
tell active project document
set projectPath to path as string
end tell
end tell
return projectPath
END
)
cd "$result"
/Developer/clangchecker/scan-build -k -V xcodebuild -configuration Debug -sdk iphonesimulator3.0
Obviously, you will need to adjust the path to your install of Clang, and adjust to the version of the SDK you are using.
Remember to do a "Clean All" immediately before using scan-build, or the results may be incomplete.
mmc
2009-06-07 13:05:16
Every time I run this script, I must restart Xcode to run it again. Why? Is there a way to run the script twice without restarting? It won't allow me to call it again!
HelloMoon
2009-09-03 12:07:53
Hmmm.... I never had that problem... HOWEVER: This feature is built into XCode 3.2, I would simply upgrade, and forget this script altogether.
mmc
2009-09-03 14:38:01
A:
I believe the ${PROJECT_DIR} environment variable is what you want for the directory of the project running a build-phase script.
Barry Wark
2009-06-07 15:19:02
${PROJECT_DIR} will work in a build phase script, yes, but not in a user script that can be triggered from the script menu.
mmc
2009-06-07 15:26:30
Yes, your question was very clear. Sorry. You could still create a clang target in your project (this is what I usually do). Not as clean as a menu script (and you have to create one in each project, of course), but it works well.
Barry Wark
2009-06-08 03:59:32
Ah ha! I had not even thought of establishing a separate target. Lots of different ways to approach this one, I guess.
mmc
2009-06-08 23:43:10
A:
FYI, Xcode 3.2 (Snow Leopard only I believe) includes the Clang Static Analyzer in the "Build and Analyze" menu option.
http://iphonedevelopertips.com/xcode/static-code-analysis-clang-and-xcode-3-2.html
One downside of Xcode 3.2 (aside from it only working on Snow Leopard) is that the v2.x Simulators don't seem to work - in fact, I've seen posts indicating that v2.x builds are not supported at all.
Dan J
2010-02-10 17:46:25