[libgpg-error PATCH] doc: if ever, depend on yat2m$(EXEEXT)

NIIBE Yutaka gniibe at fsij.org
Tue Jul 10 04:12:33 CEST 2018


Thanks for your patch.

Michael Haubenwallner <michael.haubenwallner at ssi-schaefer.com> writes:
> * doc/Makefile.am (CROSS_COMPILING, HAVE_YAT2M): Set empty YAT2M_DEP.
> (not CROSS_COMPILING): Ignore detected yat2m, use local one.  Use EXEEXT
> in YAT2M_DEP rather than explicit '.exe' based on HAVE_W32_SYSTEM.

I agree that using EXEEXT is better than HAVE_W32_SYSTEM.  Also, I agree
that we don't need to use detected yat2m for !CROSS_COMPILING.

Furthermore, I also think that the detection of yat2m on build system is
not needed for CROSS_COMPILING now, because we can build

Remaining problem is we need to have something like EXEEXT for build
machine, so that we can support cross building on Windows (say, for
POSIX machine).

Here is my attempt.  How do you think?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-doc-Now-yat2m-is-a-standard-tool-provided-by-libgpg-.patch
Type: text/x-diff
Size: 1674 bytes
Desc: patch 0001
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20180710/8b341873/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-build-Use-AX_CC_FOR_BUILD-and-EXEEXT.patch
Type: text/x-diff
Size: 5644 bytes
Desc: patch 0002
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20180710/8b341873/attachment-0001.patch>

More information about the Gnupg-devel mailing list