D13613: RFC: Fix libclang default include paths on FreeBSD.

[Aaron Puchert]

aaronpuchert added a comment.


  That's the part I don't understand. Why is the C++ standard library include directory `/usr/include/c++/v1/` builtin, but the C standard library directory `/usr/include` isn't? Here's what I get:
  
    clang -ferror-limit=100 -fspell-checking  -Wunused-parameter -Wunreachable-code -Wall -std=c++11 -nostdinc -nostdinc++ -xc++ -isystem/usr/include/c++/8 -isystem/usr/include/c++/8/x86_64-suse-linux -isystem/usr/include/c++/8/backward -isystem/usr/local/include -isystem/usr/include -isystem /usr/lib64/clang/6.0.0/include -imacros /tmp/test_problems.HeYwcT /tmp/testfile_LwSiAq.cpp

INLINE COMMENTS

> parsesession.cpp:269
>  
>      addIncludes(&clangArguments, &smartArgs, includes.system, "-isystem");
>      addIncludes(&clangArguments, &smartArgs, includes.project, "-I");

This is where `/usr/include` comes from on Linux. Can you find out why `includes.system` is (apparently) incomplete on FreeBSD?

REPOSITORY
  R32 KDevelop

REVISION DETAIL
  https://phabricator.kde.org/D13613

To: arrowd, #kdevelop, mwolff
Cc: mwolff, aaronpuchert, kdevelop-devel, antismap, iodelay, vbspam, njensen, geetamc, Pilzschaf, akshaydeo, surgenight, arrowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20180702/fba7050e/attachment.html>