On Fri, Jan 19, 2018 at 2:37 PM, Alexei Podtelezhnikov <[email protected]> wrote: > Hi again, > > My msys2 builds produces the following: > > libfreetype.a (static) > libfreetype.def > > libfreetype.dll.a (import)
that's the way libtool name the import library. The gnu linker (ld) looks at that name so no problem here (see https://sourceware.org/binutils/docs-2.17/ld/WIN32.html ("direct linking to a DLL" section)) Vincent > msys-freetype-6.dll > msys-freetype-6.dll.def > > This looks a bit strange. Do we (or libtool?) forget to rename > libfreetype.dll.a? Is this so called import library? The import > library has been produced only recently after we added > dllimport/dllexport. > > My MSVC builds produce > > freetype.lib (static) > > freetype.lib (import) > freetype.dll > > I do not like that the naming is inconsistent altogether. Any suggestions? > > Alexei > > > > > Alexei _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
