<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - package scan-build with compiler"
href="http://llvm.org/bugs/show_bug.cgi?id=21764">21764</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>package scan-build with compiler
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>3.5
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Static Analyzer
</td>
</tr>
<tr>
<th>Assignee</th>
<td>kremenek@apple.com
</td>
</tr>
<tr>
<th>Reporter</th>
<td>legalize@xmission.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>The static analysis tools are very important and useful and should be packaged
in the binary packages provided:
shell 26> xz -d < clang+llvm-3.5.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz | tar
tvf - | fgrep scan
shell 27>
I really would like to use scan-build on my open source projects via the
travis-ci.org continuous integration build servers, but it is really going to
bog things down if I have to build clang from source every time I do a build.
Yes, I could do my own build and push the binary package somewhere, but that is
what I expect from the binary builds produced by the llvm releases.
Enabling the use of scan-build for github projects via the easy travis-ci.org
building would massively increase the user base of the static analyzer and lead
to much more rapid improvement of it, IMO.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>