Re: adding a supported compiler

[René J . V . Bertin]

On Saturday January 7 2017 06:36:26 Ryan Schmidt wrote:

>portconfigure.tcl

Thanks. Looks like a bit of monks' work to add it the right way :)

BTW, how good is the base clang driver at determining the language type from 
extension or syntax? IOW, can I use a single clazy wrapper that invokes 
clang-mp-x.y or do I absolutely need to use clang++-mp-x.y for C++ and ObjC++?

An example where being able to get advanced diagnostics from a user's machine 
*might* come in useful:
https://bugs.kde.org/show_bug.cgi?id=374568

R.

Re: adding a supported compiler

[Ryan Schmidt]

> On Jan 7, 2017, at 05:23, René J.V. Bertin  wrote:
> 
> Morning!
> 
> I've created a port for clazy (https://github.com/KDE/clazy) which provides 
> an additional layer of code analysis on top of what clang already can do.
> 
> This is a compiler wrapper, so it can be used in a normal build cycle to get 
> additional diagnostics while building code. I'd like to be able therefore to 
> do something like `configure.compiler=clazy-3.9` for certain of my projects, 
> at least locally.
> 
> Where would I make the necessary changes to make that possible?

portconfigure.tcl

adding a supported compiler

[René J . V . Bertin]

Morning!

I've created a port for clazy (https://github.com/KDE/clazy) which provides an 
additional layer of code analysis on top of what clang already can do.

This is a compiler wrapper, so it can be used in a normal build cycle to get 
additional diagnostics while building code. I'd like to be able therefore to do 
something like `configure.compiler=clazy-3.9` for certain of my projects, at 
least locally.

Where would I make the necessary changes to make that possible?

Thanks,
R.