D12331: Always use the clang builtin headers for the libclang version we use

Aleix Pol Gonzalez noreply at phabricator.kde.org
Thu Apr 19 23:37:04 UTC 2018

apol added a comment.

  > - what compiler is used?
  I'm using clang for all my projects.
  > - what do we get from the IADM as include paths, defines and arguments?
  Is there an easy way to query it?
  > - can you show a minimal test file and the errors reported by clang?
  it was litterally plagued with errors such as:
    Problem in Semantic analysis
    Use of undeclared identifier 'FlatpakNotifier'; did you mean 'std::FlatpakNotifier'?
    Hint: 'std::FlatpakNotifier' declared here
  I decided to clean my .cache/kdevduchain and now it works properly, so maybe it's a matter of bumping the version. *shrug*


> mwolff wrote in libclang_include_path.h.cmake:22
> I don't know what you mean? We are interested in the directory that fits to the libclang we link against.

Okay, doesn't make a lot of sense from my ignorant perspective. :P

It sounds to me like we should be telling about the system we are targetting. In fact, I'm surprised that sysroot isn't necessary.

  R32 KDevelop


To: mwolff
Cc: apol, mschwarz, brauch, kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20180419/fc7d724c/attachment.html>

More information about the KDevelop-devel mailing list