On 10/02/2012 18:44, Krzysztof Kosiński wrote:
2012/2/10 LucaDC <dicappello@...2144...>:
I see from build.xml that bin/intl.dll is copied both as intl.dll and libintl-2.dll. Now Inkscape asks for both intl.dll and libintl-8.dll: should they be the same?
I changed the build.xml in the stable branch to remove libintl-2.dll. I forgot to make the same change in trunk, sorry. intl.dll and libintl-8.dll are currently not the same.
The two files intl.dll and libintl-8.dll under devlibs are different (intl.dll is the old libintl-2.dll). In other words: should the new libintl-8.dll overwrite the old intl.dll? In this case I think it would be better to copy libintl-8.dll as intl.dll under Inkscape, not the opposite, so when it changes the correct file is always taken. And is it necessary to have the same file copied twice with different names?
DLLs on Windows are linked by name. Inkscape and one of the other libraries (don't remember which one) link against libintl-8.dll while the GTK stack links against intl.dll, and so we need both. This is can be solved by renaming libintl-8.dll to intl.dll and regenerating the import library.
However at the moment there is a compilation problem in Gettext that causes libintl-8.dll not to export the symbol libintl_printf, which is required by the GTK stack - instead the bogus symbol __printf__ is exported. I think I have this fixed, but configuring Gettext takes around half an hour in my Windows VM, so I didn't verify it yet.
Could someone please review this report against r10990:
Bug #933833 in Inkscape: “libintl-8.dll and libiconv-2.dll not found” https://bugs.launchpad.net/inkscape/+bug/933833
and adjust the build routines if needed to make sure that the installer for the upcoming release builds as well as newer development builds for Windows include all required libs?
thx, ~suv