[dvipdfmx] [PATCH] mingw: Don't copy libtool wrappers
Shunsaku Hirata
shunsaku.hirata74 at gmail.com
Sun Oct 31 04:07:08 CET 2021
Hi Karl,
2021年10月31日(日) 5:22 Karl Berry <karl at freefriends.org>:
>
> install-exec-hook: install-bin-links
> if WIN32
> - $(INSTALL_PROGRAM) call_xdvipdfmx$(EXEEXT) $(DESTDIR)$(bindir)/dvipdfm$(EXEEXT)
>
> Any idea why this install-exec-hook exists in the first place?
> I don't see it for other programs in the TL tree.
I don't know how this was introduced.
However, if you just want to know why such a wrapper is needed:
dvipdfmx changes it's behavior depending on the program name
it was called, e.g., it behaves as extractbb when "xdvipdfmx.exe"
is called through the wrapper "extractbb.exe".
I think this Windows specific behavior comes from the autoconf
macro "KPSE_WIN32_CALL" described in the following page:
https://www.tug.org/texlive/doc/tlbuild.html#Macros-for-Windows
A wrapper is used just to emulate symbolic links on Windows
platforms.
Thanks,
Shunsaku Hirata
More information about the dvipdfmx
mailing list.