Re: [Mingw-w64-public] Compiling packages with MinGW 32 and 64 bits

Thank you, now I know how to compile gettext for windows. Why so mystical ? -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve

Re: [Mingw-w64-public] gendef - why?

Op 9 dec. 2012 10:51 schreef "Kai Tietz" het volgende: > > 2012/12/9 Václav Šmilauer : > > Hi, > > > > I understand gendef generates symbols from non-mingw DLLs so that linker > > knows which symbols are defined. > > This feature is already in ld. And this feature of ld shows also why > .def file

[Mingw-w64-public] Compiling packages with MinGW 32 and 64 bits

Following Ruben's feedback, I updated my documentation explaining in detail how to compile the following packages using Ruben personal build 32 and 64 bits - pkg-config lite - libiconv - zlib - bzip2 - libtool - libxml2 - libpng - libjpeg - libtiff - freetype2 - lc

Re: [Mingw-w64-public] gendef - why?

2012/12/9 Václav Šmilauer : > Hi, > > I understand gendef generates symbols from non-mingw DLLs so that linker > knows which symbols are defined. This feature is already in ld. And this feature of ld shows also why .def files are to be preferred. 1.) A .def file can be used to generate an import

[Mingw-w64-public] gendef - why?

Hi, I understand gendef generates symbols from non-mingw DLLs so that linker knows which symbols are defined. What is thereason to have gendef, instead of making the linker understand the PE(+) formats so that it can read exported symbols from the DLL directly, at link time? Technical reason