Re: New Flymake rewrite in emacs-26

[Noam Postavsky <npostavs@users.sourceforge.net>]

On Tue, Oct 10, 2017 at 1:03 PM, João Távora <joaotavora@gmail.com> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Most of the flags we use are for flagging dubious or erroneous code,
>> they should not matter, I think.
>
> I think it’s useful to have Flymake synchronized with these flags, so
> that you are notified visually of these problems ahead of a "real"
> compilation. FWIW this is what the Emacs Lisp backend already does for
> Emacs Lisp sources.
>
>> What compiler flags must be set for Flycheck to work reasonably well
>> with a program's sources?  I guess the -I flags, but what else?
>
> For "reasonable" operation, it’s mostly the -I flags, and maybe some
> essential -D flags (In Emacs’s case -Demacs, I think).
>
>> (I have never used Flymake, so my questions are ones of a layman in

I've also hardly ever used flymake, so this may be nonsense, but maybe
you could run 'make --just-print foo.o' to get the exact shell
commands for compiling foo.c. This would bypass any need to know
details of compilation beyond figuring out the target name from the
source.