<table><tr><td style="">aaronpuchert added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D13613">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>But <tt style="background: #ebebeb; font-size: 13px;">test_problems</tt> test doesn't use this analyzing the code. Maybe the code for the test itself should be changed?</p></blockquote>

<p>Not entirely sure, but this seems to be the right thing then. Because in the actual application, the include directories should come from the includes&defines-plugin, so there should be no need to add <tt style="background: #ebebeb; font-size: 13px;">/usr/include</tt>. The only directory that makes sense to add here is the clang-internal include directory (something like <tt style="background: #ebebeb; font-size: 13px;">/usr/lib64/clang/<version>/include</tt> usually), which <tt style="background: #ebebeb; font-size: 13px;">GccLikeCompiler::includes</tt> will <em>not</em> produce if the compiler is GCC.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R32 KDevelop</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D13613">https://phabricator.kde.org/D13613</a></div></div><br /><div><strong>To: </strong>arrowd, KDevelop<br /><strong>Cc: </strong>aaronpuchert, kdevelop-devel, antismap, iodelay, vbspam, njensen, geetamc, Pilzschaf, akshaydeo, surgenight, arrowd<br /></div>