Ping! Paul, did you have a chance to look at this issue?
> Date: Thu, 07 Nov 2019 17:29:48 +0200
> From: Eli Zaretskii <e...@gnu.org>
> Cc: bug-make@gnu.org
>
> > From: "Jannick" <thirdedit...@gmx.net>
> > Cc: <bug-make@gnu.org>
> > Date: Thu, 7 Nov 2019 12:32:23 +0100
> >
> > Subject: [PATCH 03/13] Windows build: add optional cmd line flag --exe-name
> > to
> > build_w32.bat
> >
> > This commit helps the user choose a name for the GNUMake executable
> > different from the default 'gnumake.exe' used at link time.
>
> This patches only the GCC part of the script. Does that mean the MSVC
> part already caters to your use case in some way?
>
> Paul, I think we have a situation here, most probably my fault.
> Currently, we produce the executable named gnumake.exe, but we install
> it as something else, like make.exe, which means the importy library
> will not work, because the name gnumake.exe is hard-coded in the
> import library when we build it. I think I failed to consider this
> aspect when I implemented the Windows support of shared object
> loading.
>
> Does the same problem exist with the MSVC builds? If not, how this
> issue is resolved in that case?
>
> One solution of this would be to also build a DEF file, and tell users
> to edit the name of the executable in that file and then create an
> import library from the DEF file using dlltool, if they rename the
> executable.
>
> Another solution is the 3rd patch sent by Jannick, but I like his
> solution less because it doesn't allow to rename the executable after
> it is built.
>
> WDYT?
>
>
