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:28 UTC 2018

apol added a comment.

  In D11136#221589 <https://phabricator.kde.org/D11136#221589>, @mwolff wrote:
  > ugh sorry, I apparently just thought about this for real the first time... people (like me sometimes) often use GCC for compiling. But our language support is notoriously _bad_ at trying to cope with the gcc compiler environment. So we may actually now see *more* issues than before, no? Do we really want this? Hmm I was actually thinking about _removing_ most of the non-clang compiler stuff (builtin macros, includes etc) - but I'd like to discuss this first
  Well the whole point here is to make sure that we are running the same as the project. So if the alternative is using /opt/android-ndk/...../something-gcc or /usr/bin/clang. Yes, we want gcc.

  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/f390cd20/attachment.html>

More information about the KDevelop-devel mailing list