Re: Clang warns on "wrong" header guard in "config.h"

[Alexandre Julliard]

Charles Davis  writes:
> These lines generate what Clang thinks is the header guard for the
> "config.h" header, but we know that it isn't--that header AFAICT has
> never had an include guard, and __WINE_CONFIG_H is just there to
> indicate that it's been included. Should we change the __WINE_CONFIG_H
> macro to be a real header guard instead, or (as I'll admit it has been
> in the past) is Clang broken here?

You can try to add a real guard if it helps, but of course the
WINE_CROSSTEST ifdef has to remain.