On Sun, Mar 25, 2012 at 7:31 PM, jeremy hunt <jere...@optimation.com.au> wrote: > Thomas J. Hruska wrote: >> >> On 3/23/2012 12:53 AM, jeremy hunt wrote: >>> >>> This posting is to help people to build OpenSSL 1.0.1 with Microsoft >>> Visual Studio. It may also indicate a required change to the build >>> instructions >>> for Microsoft Visual Studio. >>> >>> Summary: >>> ---------- >>> I found I needed to install the Windows SDK and manually configure my >>> build environment to successfully build OpenSSL 1.0.1 >>> >>> Details: (cut out for this reply, refer to my original posting if you >>> need help) >>> >>> Regards, >>> >>> Jeremy >> >> >> If you had to do that, then your command line build environment on your >> new machine was not set up correctly to begin with. Most modern projects >> would probably not have built (not just OpenSSL). As a Windows developer, >> the Windows SDK is an implied requirement for any project. >> > Thanks for that Thomas. Generally what you say in this list is good but in > this case I do not think your statement is very helpful. It would be more > collaborative to suggest a way to do that just for those people who have > missed it, ... as I attempted to do in my original posting. I was pointing > out that the standard tools did not do that for you. Perhaps you do not use > the Microsoft Visual Studio Command Prompt Window for builds as I do. > > If there is a previous requirement for a build, the documentation generally > states it. I am trying to help by suggesting a small change in the > documentation which might cut down questions in this list. If you think > things that you take for granted are too trivial to tell the list, that is > fine. I prefer to let people know problems I have had in the past in the > hope it will help some of them and make them and this list more productive. > > By the way I had built a number of other Windows products on the new build > environment before building OpenSSL, ... successfully and without the > Windows SDK. As I stated it was a new build environment. OpenSSL was the > fifth product I had built on the new environment and the first that required > the Windows SDK, so I am unsure if I agree with your statement. Wouldn't it > be better to explicitly state the requirement, rather than rely on previous > knowledge. Personally I am surprised that OpenSSL uses a native crypto lib, > not that I have investigated why. Just guessing: CryptGenRandom function to help gather entropy (http://msdn.microsoft.com/en-us/library/windows/desktop/aa379942(v=vs.85).aspx). I know OpenSSL can also do a heap walk, too. Perhaps it does both.
I also believe OpenSSL interacts with Windows certificate store. Jeff ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
