D11136: Make sure we use the same compiler settings as the project is by default

Aleix Pol Gonzalez noreply at phabricator.kde.org
Fri Mar 9 15:55:57 UTC 2018

apol added a comment.

  In D11136#221634 <https://phabricator.kde.org/D11136#221634>, @aaronpuchert wrote:
  > The Clang developers work really hard on compatibility with both GCC and MSVC, but I don't think they want to use the same defines and includes for that. For example, both Clang and GCC have their own private header files (on my machine, `/usr/lib64/gcc/x86_64-suse-linux/7/include` and `/usr/lib64/clang/5.0.1/include/`). These are quite similar, but not interchangeable. I don't think one can use one set of headers with the other compiler.
  > For the most part, I also use GCC as compiler, but I configure KDevelop to behave like Clang. Yes, my compiler will see something slightly different. So what? What matters is that both GCC and KDevelop's libclang parser implement the same C++ standard.
  > Since there is `clang-cl`, I assume that Clang can also imitate MSVC to some extent. But I don't think spying on `cl`s defines and includes and feeding them into libclang is necessary or sufficient for that. (Consider MS inline assembly, which Clang understands - but not by setting some defines.)
  I'll make sure it's not clang-cl.

  R32 KDevelop


To: apol, #kdevelop, mwolff
Cc: aaronpuchert, mwolff, kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20180309/e97bd6cc/attachment.html>

More information about the KDevelop-devel mailing list