On Wed, 29 Dec 2021, Martin Storsjö wrote:
On Wed, 29 Dec 2021, Gisle Vanem wrote:
So now, I'm trying to use the above imp-libs in
a MSVC x86 'link.exe' step. The 'hsmodem.exe' program links
fine, but running it fails with missing 'codec2_bits_per_frame'
etc.
I believe this is a known issue
Re-cc:ing the list, for public closure of the issue,
On Thu, 30 Dec 2021, Gisle Vanem wrote:
Hmm, that's quite strange - is there any difference if you'd name the
file liquid32.dll.a instead of liquid32_imp.lib? Because technically,
the new file you generated and the one from --out-implib
On Wed, 29 Dec 2021, Gisle Vanem wrote:
Martin Storsjö wrote:
In the meantime, when you create your regular import library with an
option like -Wl,--out-implib,libfoo.dll.a, add the
option -Wl,--output-def,foo.def. After that, run "dlltool -d foo.def -l
libfoo.dll.a". This recreates the
Martin Storsjö wrote:
In the meantime, when you create your regular import library with an option like -Wl,--out-implib,libfoo.dll.a, add the
option -Wl,--output-def,foo.def. After that, run "dlltool -d foo.def -l libfoo.dll.a". This recreates the import library
in a form that works better
Hi,
On Wed, 29 Dec 2021, Gisle Vanem wrote:
So now, I'm trying to use the above imp-libs in
a MSVC x86 'link.exe' step. The 'hsmodem.exe' program links
fine, but running it fails with missing 'codec2_bits_per_frame'
etc.
I believe this is a known issue with import libraries created by ld.
Hello Gnu exports.
I ned help figuring out an issue with using
a set of MinGW generated import libraries in a
MSVC program (called 'hsmodem.exe'; "High-sped Modem").
I'm not using MinGW-w64, but TDM-gcc (gcc 10.3.0).
Hopefully they are similar in this regard.
I've built these using MinGW (which
