There shouldn't be any functional difference between the import library created by dlltool and the one produced by the linker itself. Keep installing it with both names though, for compatibility with users that expect both to exist. The dlltool step was added in ec10a9ab4; prior to that, a MSVC compatible import library was generated using lib.exe. After that commit, there was no functional difference between the two import libraries (and since MSVC 2012, link.exe works just fine with the GNU binutils generated one). Signed-off-by: Martin Storsjö <martin@martin.st>pull/272/head
parent
91760a9340
commit
67c72f08a4
1 changed files with 1 additions and 8 deletions
Loading…
Reference in new issue