Compiler settings

Milian Wolff mail at
Sat Jun 7 11:54:59 UTC 2014

On Saturday 07 June 2014 11:04:36 Sergey Kalinichev wrote:
> Hi Milian!

Hey Sergey!

> >I just noticed that KDevelop now picks clang by default to find include
> >paths etc. pp.
> That not exactly the case. Actually it goes through all compilers (in
> alphabetic order) and selects the first one that is installed. So, if
> you don't have the Clang installed it'll select another compiler.

Right, what I meant is that when you have both installed you'll get Clang even 
though it should be GCC.

> >Furthermore, I notice that the compiler combobox in the project settings
> >does not filter non-existing compilers. I see MSVC on a Linux machine
> >which is of course wrong. And of course users might see GCC/Clang even
> >though they are not installed.
> Thats the truth. But what about cross-compilation? In that case the
> compiler is not installed in the default directory (e.g. Android NDK
> comes with the GCC compiler). So imo it still makes sense to make
> those items available. Otoh if the path to the compiler is wrong,
> probably it makes sense to show some kind of warning then.

True, I didn't think about that :) But at least MSVC could/should be hidden on 
Linux, or is there a way to use MSVC on Linux (Wine?).
> >Furthermore, I have to remind you once more that blogging and regular
> >status updates are mandatory during GSOC. Please do get an account on
> > and introduce yourself, your project and the good work you
> >did so far!
> Yes, I know, I know... I've already done the initial blog:
> Also I've added it to the "Planet KDE": r1386072
> Long story short - will update the status report and fix the compiler
> issues this Wednesday or Thursday.

Cool, sounds good.

Thanks & Bye

Milian Wolff
mail at

More information about the KDevelop-devel mailing list