Lines Matching full:build

1 scan-build
4 A package designed to wrap a build so that all calls to gcc/clang are
6 the clang static analyzer. Includes intercept-build tool, which logs
7 the build, as well as scan-build tool, which logs the build and runs
30     $ scan-build <your build command>
34     $ intercept-build <your build command>
39     $ analyze-build
49     $ intercept-build <your build command>
54     $ analyze-build --ctu
62     $ analyze-build --ctu-collect-only
65     $ analyze-build --ctu-analyze-only
73 Generally speaking, the `intercept-build` and `analyze-build` tools together
74 does the same job as `scan-build` does. So, you can expect the same output
75 from this line as simple `scan-build` would do:
77     $ intercept-build <your build command> && analyze-build
79 The major difference is how and when the analyzer is run. The `scan-build`
87 2.  Use special library to intercept compiler calls during the build process.
88     The analyzer run against each modules after the build finished.
91 3.  Use compiler wrappers to intercept compiler calls during the build process.
92     The analyzer run against each modules after the build finished.
96 The 1. and 3. are using compiler wrappers, which works only if the build
97 process respects the `CC` and `CXX` environment variables. (Some build
99 you need to pass the compiler wrappers manually. eg.: `intercept-build
101 original build command would have been `make all` only.)
103 The 1. runs the analyzer right after the real compilation. So, if the build
115 `intercept-build` command uses only the 2. and 3. mode to generate the
116 compilation database. `analyze-build` does only run the analyzer against the
125 variables might not work. (I don't know any build tool which does that, but
145   [2]: https://pypi.python.org/pypi/scan-build