[bind10-dev] WIN32 port

[Danny Mayer]

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?

> 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.

>> 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.

>> I am guessing we will not use autoconf/automake suite on Windows
>> ... or are we?
>

While it can be done it's almost not worth the effort.

> => you guess right: there is a stack of Visual Studio project files
> (and >70 different projects). Usually the VS GUI/IDE is used but
> there is a batch (aka command line) tool 'MSBuild' which makes this
> phase "scriptable".
> 

MSBuild makes things very simple.

Danny