[Geany-Devel] Plugins Quality Check

[Colomban Wendling]

Le 21/02/2014 16:39, Matthew Brush a écrit :
> On 14-02-21 06:30 AM, Colomban Wendling wrote:
>> Le 21/02/2014 03:16, Lex Trotman a écrit :
>>> [...]
> 
> OK, I didn't think it was OK to assume GCC was the compiler,

It isn't, indeed.  Although well, to be fair we probably have no idea
what happens if it's not GCC-like.  Or maybe I even remember there was
problems with MSVC?

> so I wasn't sure how you'd portably (across compilers) tell the
> compiler flags without doing a bunch of configure checks to see
> whether the compiler accepted such flags or something.

Well, basically, you can't.  Hence the bunch of configure checks --
although the ones we already have are only for GCC flags, because I
didn't know what other compilers used.

> My GCC/Clang-specific idea was to maybe just use something like
> `-Xcc=-w` or whatever in one of the VALAFLAGS variables to disable
> all warnings related to Vala code, though I'm not sure if Autotools
> invokes the C compiler via Valac or independently.

AFAIK, Autotools generate C source from vala, and the build the C
sources.  It's pretty obvious when you see it adds C sources to the
distribution I guess :)

>>> [...]
>>>> 
>>>> The GTK2 Vala binding is deprecated, same as the GTK2 C
>>>> API/library. There is a compiler flag for Valac to make it
>>>> disable the deprecation warnings, if that is desirable.
>> 
>> Is there really a flag to only disable deprecated warnings?  IIRC
>> there is only --disable-warnings, and IIUC it removes everything
>> not an error?
>> 
> 
> I believe Valac's --disable-deprecated option will disable it
> warning about deprecated annotations in the VAPI files. I'd have to
> test it to be sure though.

Oh, I believe it disabled all deprecated features -- rather the contrary
then.  But I'm not sure either.

Cheers,
Colomban