[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [build_w32.bat] feature request: add optional command line argument
From: |
Eli Zaretskii |
Subject: |
Re: [build_w32.bat] feature request: add optional command line argument for executable name |
Date: |
Mon, 04 Nov 2019 05:35:46 +0200 |
> From: "Jannick" <address@hidden>
> Cc: <address@hidden>
> 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 cannot resolve the symbols expected to be
> provided by the executable calling the plugin.
And how do you suggest to fix this?
- [build_w32.bat] feature request: add optional command line argument for executable name, Jannick, 2019/11/03
- Re: [build_w32.bat] feature request: add optional command line argument for executable name, Eli Zaretskii, 2019/11/03
- RE: [build_w32.bat] feature request: add optional command line argument for executable name, Jannick, 2019/11/03
- Re: [build_w32.bat] feature request: add optional command line argument for executable name,
Eli Zaretskii <=
- RE: [build_w32.bat] feature request: add optional command line argument for executable name, Jannick, 2019/11/07
- Re: [build_w32.bat] feature request: add optional command line argument for executable name, Eli Zaretskii, 2019/11/07
- Re: [build_w32.bat] feature request: add optional command line argument for executable name, Eli Zaretskii, 2019/11/15
- Re: [build_w32.bat] feature request: add optional command line argument for executable name, Paul Smith, 2019/11/19
- Re: [build_w32.bat] feature request: add optional command line argument for executable name, Eli Zaretskii, 2019/11/19