> From: "Jannick"
> Cc:
> Date: Sun, 3 Nov 2019 22:01:06 +0100
>
> > In particular, can you show how the hard-coded name of the executable
> > prevents linking against the import library?
>
> As said above, the issue is not about linking the dll (which should always
> work), but that the plugin
Hi Eli,
Many thanks for looking into this!
On Sun, 03 Nov 2019 17:35:42 +0200, Eli Zaretskii wrote:
> > From: "Jannick"
> > Date: Sun, 3 Nov 2019 13:30:11 +0100
> >
> > Would it be possible to pass to build_w32.bat in an optional command
> > line argument the executable name (currently hard code
> From: "Jannick"
> Date: Sun, 3 Nov 2019 13:30:11 +0100
>
> Would it be possible to pass to build_w32.bat in an optional command line
> argument the executable name (currently hard coded in the variable MAKE as
> 'gnumake')?
>
> When creating a plugin (.dll) with GCC (by linking against gnumake
Hi,
This is a pure Windows issue:
Would it be possible to pass to build_w32.bat in an optional command line
argument the executable name (currently hard coded in the variable MAKE as
'gnumake')?
When creating a plugin (.dll) with GCC (by linking against gnumake.dll.a)
which should then be called
