[bind10-dev] bug in Encode/Decode stuff

[Francis Dupont]

> I now started working on the ticket of 838, it seems that you have done
> a lot of work to compile bind10 on windows, can you share the VS project
> files with me? Thanks.

I saved them in the trac829 branch but:
 - you should read my notes in trac827 (win32build/README,
  note it was written before I tried VS 2008)
 - I have no yet done them for VS 2005
 - there is unfinished stuff for python (look at trac839, note the
  debug python is not installed by default so it doesn't link in Debug)
 - there is unfinished stuff for libcc (so if you have a project about
  cc it must be disabled as it won't build)
 - the build logs are attached to the #858 ticket
 - 836 must be fixed before (Jinmei is working on it, it is pretty
  trivial but I don't know its status)
 - 837 must be fixed before too (far more a problem)
Without 836 it crashes at runtime, without 837 it doesn't fully build.
With 836, 837 and 838 it builds at the exception of the Debug python
(just because I don't have the required python32_d.lib file) and of
course libcc and everything which can be built successfully run
(the Release python too with a lot of warnings about unclosed files).

About 838 the proposed fix works (both fix parts in fact, the first one
uncovers a Windows specific issue addressed by the second).
Don't believe that because the fix is simple it was simple to find it (:-).
(I like elegant fixes a bit too much!)

Thanks

Francis Dupont <fdupont at isc.org>

PS: I (ab)use a virtual machine from ISC labs (a Windows Server 2008 which
was installed to fix a crazy socket API feature introduced by Microsoft),
I can share what you want (the bind10 source file I use for instance),
I have a rdesktop window open on it... The only issue should be the
timezone (I am in UTC + 2) but please ask!

PPS: some notes about trac829:
 - BINDInstall is a fake application (my idea was to copy the bind9
  application with the same name but today it is just the main project)
 - I kept a dllmain.cc but it is useless now
 - it is not clear the config.h could be shared between VS versions
  (and it is not really finished, it just currently works)
 - there are some hard paths (as little as possible but I haven't yet
  write the needed perl scripts to update them, so you'll have to
  fix them manually (or to write the perl scripts :-))

PPPS: you have to begin first with the google test (pretty hairy,
i.e., far too easy to get it wrong :-). I really prefer the msvc
way (this removes the CMake dependency BTW).

P^4S: if you rebuild Python, can you send the python32_d.lib file to me?