Created
February 28, 2013 04:28
-
-
Save gavrix/5054182 to your computer and use it in GitHub Desktop.
Script integrating OCLint into XCode. Put it in "Run script" build phase.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
source ~/.bash_profile | |
hash oclint &> /dev/null | |
if [ $? -eq 1 ]; then | |
echo >&2 "oclint not found, analyzing stopped" | |
exit 1 | |
fi | |
cd ${TARGET_TEMP_DIR} | |
if [ ! -f compile_commands.json ]; then | |
echo "[*] compile_commands.json not found, possibly clean was performed" | |
echo "[*] starting xcodebuild to rebuild the project.." | |
# clean previous output | |
if [ -f xcodebuild.log ]; then | |
rm xcodebuild.log | |
fi | |
cd ${SRCROOT} | |
xcodebuild clean | |
#build xcodebuild.log | |
xcodebuild | tee ${TARGET_TEMP_DIR}/xcodebuild.log | |
echo "[*] transforming xcodebuild.log into compile_commands.json..." | |
cd ${TARGET_TEMP_DIR} | |
#transform it into compile_commands.json | |
oclint-xcodebuild | |
fi | |
#if [-d report.html]; then | |
#rm report.html | |
#fi | |
#run static analyzer | |
#oclint-json-compilation-database -- -o=./report.html -html | |
echo "[*] starting analyzing" | |
cd ${TARGET_TEMP_DIR} | |
oclint-json-compilation-database | sed 's/\(.*\.\m\{1,2\}:[0-9]*:[0-9]*:\)/\1 warning:/' | |
It was tested on Xcode that was out 6 years. I'm sorry, I haven't tried on newer Xcode since then.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
when using this with xcode, it has to run xcodebuild twice. is there any way to get the existing output from xcodebuild?