| commit | fc63d72032890cd1923d8157aa9a797d205f6b5d | |
| author | Christophe CURIS <christophe.curis@free.fr> | |
| Thu, 13 May 2021 15:20:24 +0000 (13 17:20 +0200) | ||
| committer | Carlos R. Mafra <crmafra@gmail.com> | |
| Tue, 18 May 2021 16:49:17 +0000 (18 17:49 +0100) | ||
| tree | ca1c1ea33eaffda9c728a8821f3cc2588ddd2c1b | treesnapshot (tar.gz zip) |
| parent | eb2a9d97a26c994ec7c582a2762c6d88aa401122 | commitdiff |
WINGs: Fix incorrect use of macro USE_PANGO in installed header
The header "WINGsP.h" needs different behaviour depending on whether the
support for Pango was enabled or not. But the related macro USE_PANGO is
defined by WindowMaker's configure, and after this header have been
installed the macro is no more valid.
This patch makes the "WINGsP.h" a generated file, so it will be different
depending on USE_PANGO, but will not make use of the macro itself.
As a side effect of being now generated, the include paths in the makefile
have been updated to include build-dir too, because for users doing an
out-of-tree build the generated file (that is used during compilation) is
placed in the build-dir.
Signed-off-by: Christophe CURIS <christophe.curis@free.fr>
The header "WINGsP.h" needs different behaviour depending on whether the
support for Pango was enabled or not. But the related macro USE_PANGO is
defined by WindowMaker's configure, and after this header have been
installed the macro is no more valid.
This patch makes the "WINGsP.h" a generated file, so it will be different
depending on USE_PANGO, but will not make use of the macro itself.
As a side effect of being now generated, the include paths in the makefile
have been updated to include build-dir too, because for users doing an
out-of-tree build the generated file (that is used during compilation) is
placed in the build-dir.
Signed-off-by: Christophe CURIS <christophe.curis@free.fr>