Documentation on W32
lrn1986 at gmail.com
Sat Sep 15 11:37:01 CEST 2012
-----BEGIN PGP SIGNED MESSAGE-----
On 15.09.2012 13:18, Nikos Mavrogiannopoulos wrote:
> On 09/15/2012 11:11 AM, LRN wrote:
>>> I'm wondering what is Loaded_CertEnumCRLsInStore() that you
>>> use instead of CertEnumCRLsInStore()? If the mingw32 issue is
>>> widespread I could include that patch in gnutls.
>> MinGW Win32API package does not have CertEnumCRLsInStore()
>> prototype in its headers (easily fixable by declaring the
>> prototype yourself) AND it doesn't export CertEnumCRLsInStore()
>> in its import library for crypt32. THAT is the real problem. The
>> only way to fix that is to patch mingw w32api package and rebuild
>> it. I can't tell users to recompile one of the most basic
>> packages in their system, obviously. Submitting a patch to
>> mingw.org takes efforts, it will be in the queue for some unknown
>> amount of time, and then one will have to wait for the next
>> win32api release.
>> Very little fun in that.
> Indeed. Is there any reason for not using mingw64-32 instead?
No reason other than compatibility.
Mingw.org has been around longer than mingw-w64, and most packages
that aimed at W32 targeted mingw.org. They are similar, but not
identical, and migrating to mingw-w64 means porting some small things
in 100 packages all over again.
Also, mingw.org are the ones who made and continue to maintain MSys,
which is still the only way (other than Cygwin) to build on W32, so
mingw.org is the obvious toolchain to use with MSys.
And finally, mingw-w64 only recently started to supply native
toolchains. Before that mingw-w64 was always an x86 toolchain that
cross-compiled to x86_64. Cross-compilation is extra tricky, and i
prefer native toolchains (like mingw.org).
Also, i have some things on my hands that i'd like to resolve before
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the Gnutls-devel