Hello,
I'm preparing for future gnutls integration which says in the next stable release, it'll be using nettle by default. I'm working on Windows builds and the 2.1 release has several problems. I'm not entirely familiar with the autotools, so I don't know exactly where the problem lies - but it generates shared library names in the unix/linux style (e.g. libnettle.so.4) instead of Windows-style: libnettle-4.dll. I can simply rename the dll and it'll work, but it's a pain and not in line with most other open source projects.
Also, when I use --enabled-shared --disable-static, my configure options are not respected. That is, it builds a static lib as well as the (incorrectly named) shared library. A .dll.a lib file is not created. When I use typical configure options such as --prefix= --libexecdir= --bindir= --libdir= --includedir=, they're not honored. e.g. I specified a different bindir for the shared libs, yet they still ended up in the --libdir directory.
This may result from the use of an older autotools/libtool setup, but I'm unsure.
I'm building natively using GCC 4.5.1 (x86, 32-bit) from the MinGW-w64 folks on Windows 7 64-bit.
Thanks, - David Hoyt