[bind10-dev] bug in Encode/Decode stuff

[Danny Mayer]

On 4/22/2011 9:08 AM, Francis Dupont wrote:
>> I'm sure what you're saying makes sense from your perspective, but
>> it's completely lost on me.  There is no pre-build step required to
>> build NTP on Windows, assuming OPENSSL_INC and OPENSSL_LIB have been
>> wired into the persistent user or systemwide environment variables.
> 
> => to wire application dependent environment variables in a no way
> in the bind10 case (unfortunately the wired path are for tests so
> critically application dependent).
> This doesn't mean I don't like your idea (the python path is wired
> for instance) but it doesn't provide a full solution.
> 

There are two choices here and this is true for unix too, you either use
environmental variables to point to the OpenSSL include directory and
libraries or you require that they go into the same directory every time
you create a new version of OpenSSL. In BIND9 (see rt18632) I chose the
former and use a perl utility to create the necessary environmental
references and add them to the user's environmental variables.


>>> Now if you have a way to automagically build including with Express
>>> versions (which don't provide the command line building commands).
>>
>> They may not officially support command-line building, but it works
>> for me using VC++ 2008 EE:
> 
> => my VS C++ 2010 Express shell doesn't know vcbuild (but there is
> a msbuild? perhaps the issue is 2008 vs 2010, not Express vs paying
> versions).
> 

I haven't used VS 2010 yet though I doubt that it's very different. It's
msbuild in VS 2005 which is what I used for BIND9. From the BuildAll.bat
batch file:

msbuild BINDBuild.sln

I'm sure it exists also in 2008 though I don't have that near me at the
moment to check.

Danny

> Regards
> 
> Francis Dupont <fdupont at isc.org>