[bind10-dev] bug in Encode/Decode stuff

[Francis Dupont]

> On Fri, Apr 22, 2011 at 09:51 UTC, Francis Dupont <fdupont at isc.org> wrote:
> > - it is not clear the config.h could be shared between VS versions
> > (and it is not really finished, it just currently works)
> 
> For what it's worth, NTP uses a single windows config.h to build with
> VC6, VS 2003, 2005, 2008, or 2010

=> I am not sure this will work for bind10 so I began with a single
config.h and pray I never get a counter example...

 (using 2008 .sln/.vcproj files).

=> Visual Studio is not backward compatible so I don't understand
how this can work with VS 2005 for instance. BTW newer versions
are not only to make more money (:-) so IMHO it is better to be
able to use new features, i.e., not have files for the only oldest
(because compatible) version.

About bind10 IMHO we have some constraints on the OS itself, for
instance it is not interesting to try to run it on a platform
without a native IPv6 (e.g., Windows XP), so I am far to be
convinced there is an interest to support VS 2005.
BTW it works with the C++ Express *free* version, my VS 2010 is
an Express one...

> With a bit more work I suspect all the Visual Studio versions could
> share a single set of .sln/.vcproj files.

=> it is true if these files are for the oldest version (VS is
upward compatible, e.g., VS 2010 converts VS 2005 .sln/.vcproj or
even .dsw/.dsp files...)

> > - 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 :-))
> 
> Rather than rely on perl scripts to mangle your .sln/.vcproj files,
> you may be able to share universal .sln/.vcproj files which resolve
> library paths using environment variables.  For example, notice the
> references to $(OPENSSL_INC) and $(OPENSSL_LIB) in these lines from
> ports\winnt\vs2008\ntpd\ntpd.vcproj:

=> it doesn't change things: you have to run a tool before building,
i.e., it doesn't matter what the pre-build does as anyway you have
a pre-build phase... (and I am afraid you need a post-build too :-).
Now if you have a way to automagically build including with Express
versions (which don't provide the command line building commands).

Regards

Francis Dupont <fdupont at isc.org>