[bind10-dev] WIN32 port

[Francis Dupont]

> On 9/6/2012 3:44 AM, Francis Dupont wrote:
> > => yes, in fact cygwin is required (there is a sed in one build file)
> 
> You don't actually need to install cygwin in order to use sed. I have a
> copy of a Windows version of sed that does not use cygwin.
> 
> > and for instance all the check scripts are cygwin bash scripts (:-).
> 
> Why do you need bash scripts?

=> I don't really need but:
 - it is only check scripts, the equivalent of 'make check' in the bind10
  distrib
 - make itself calls scripts and in some cases the final command is itself
  a shell script
 - so it was easier than to translate all scripts from shell to cmd.exe

> > There are only a few .bat (cmd.exe batch scripts) for setting the
> > environment from a command window and the bind10 one (which
> > fails correctly to load not yet ported python tools), just to make
> > people be sure the built stuff is full Windows, i.e., can be run
> > (vs. be built) without cygwin.
> > 
> 
> It shouldn't need cygwin to build.

=> I agree but I need the equivalent of a sed so:
 - call the cygwin sed
 - install a ported sed and call it
 - install a ported perl and call it
bind9 uses the last solution but as I already have cygwin I tried the first one.
Now I believe I should add a fallback to the last one, i.e., call a .bat which
tries cygwin and if it fails perl.

> >> But how are the build (make) rules generated?
> > 
> > => it is Windows: no make!
> 
> Actually there is a make. I used it in BIND9. However that requires .mak
> files which I used to be able to generate but I don't think any of the
> newer versions of VS can generate.

=> exactly, even if nmake.exe is still available the only way to create
Makefile for it is by hand!

> MSBuild makes things very simple.

=> yes, it is the right tool for the test box.

Thanks

Francis Dupont <fdupont at isc.org>