# OCLint

> 在ios开发过程中，我们使用Clang这个前端编译工具，将OC代码输出为抽象语法树，然后编译成LLVM的bitcode，最后再编译成machine code。OCLint就是基于Clang实现的通过检查C,C++和Objective-C代码来提高代码质量、降低错误率的静态代码分析工具，代码通过OCLint检测后，可以发现一些潜在的问题。OCLint检测依赖源代码的抽象语法树来保证精准度和效率，尽可能减少误报，同时动态加载规则到系统中进行检测

## OCLint 安装

```
brew install oclint
```

## OCLint 使用

* 首先使用 xcodebuild analyze 分析代码，在用xcpretty将分析报告解析为 compile\_commands.json

```sh

xcodebuild analyze -workspace ZLGitHubClient.xcworkspace -scheme ZLGitHubClient | tee  $analyzeDirPath"/analyze.log" | xcpretty --report json-compilation-database -o $analyzeDirPath'/compile_commands.json'

```

* 使用oclint-json-compilation-database 将 compile\_commands.json 转化为可视化的报告

```sh

oclint-json-compilation-database  -p $analyzeDirPath -- -report-type pmd -o $analyzeDirPath'/report.html'

```

## 问题

* oclint: error: `Not enough positional command line arguments specified!`

解决办法 ：

在podfile中添加

```ruby
post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['COMPILER_INDEX_STORE_ENABLE'] = "NO"
        end
    end
end
```

在pod工程中将COMPILER\_INDEX\_STORE\_ENABLE改为NO

* `oclint: Not enough positional command line arguments specified!`

解决办法：<https://github.com/oclint/oclint/issues/478>

## 参考文档

[OCLint的基础使用](https://www.jianshu.com/p/6868363b6072)

[OCLint官方文档](http://oclint.org/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook.existorlive.cn/xue-xi-kai-fa-gong-ju/jing-tai-fen-xi/oclint.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.