Do we know what the motivation to rename the import library for the
Windows build was in the first place? I've tried removing the renaming
of the import library completely in the Windows build and the build
produces valid output (a valid DLL and paired import library is
generated for each RTE lib using clang build); The meson version test
addition may be unnecessary here?
Kind Regards,
John Alexander.
I looked back through the commit history for Meson and there were a
number of changes to the way that import libraries are handled between
0.47.1 and 0.54.0. I installed the meson releases in order, but was
unable to build successfully with anything before 0.54.0 - I was seeing
complaints about unknown linker flags building with Clang 11.0.0 and
Link 14.27.29112.0 from Visual Studio 2019.
Assuming that builds with meson 0.47.1 and Clang/Link do work, I took
the conservative approach of only making the change for the version of
Meson where I know that /implib is handled correctly, leaving the
previous behaviour unchanged for earlier versions which I'm unable to
verify.
Regards,
Nick
