Why are you using VC2005? I use VC10, just do the following: install MS sdk install active perl run configure per openssl INSTALL.W32 or 64 or readme open the sdk cmd window
setenv /x86 /debug /2008 nmake ms\ntddl.mak nmake ms\nt.mak note: I use /2008 switch because I use it on a 2008 server, but it is the same kernel as windows 7. I add the ENABLE-CAPIENG compile flag for capi to the make files 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: >> ------- >> I recently had to move my build machine to another PC, and I needed to >> build OpenSSL 1.0.1. >> >> I had installed MS Visual Studio 2005 on a Win XP system. >> >> I followed the excellent build instructions in the INSTALL.W32 file. I >> built from a Visual Studio 2005 Command Prompt window as I always do. >> Unfortunately my first build failed in the link phase because it >> couldn't find crypt32.lib. >> >> On further investigation I found that crypt32.lib was in the Microsoft >> SDK which I had to download and install on my build machine. >> >> I trashed my build directory and unpacked a new one, so I could go >> through the configure script with the installed SDK. I started a new >> Visual Studio 2005 Command Prompt Window for the build. Unfortunately >> the configure script did not find the SDK libraries and my build failed >> in the same place. >> >> So I manually modified the vsvars32.bat file that the "Visual Studio >> Command Prompt" uses to load its environment variables. I added: >> %Program Files%\Microsoft SDKs\Windows\7.0\Bin to PATH >> %Program Files%\Microsoft SDKs\Windows\7.0\Include to INCLUDE >> %Program Files%\Microsoft SDKs\Windows\7.0\Lib to LIB >> (On my system this file can be found in %Program Files%\Microsoft Visual >> Studio 8\Common7\Tools) >> >> Again I trashed the build directory and unpacked a new one. I started a >> new Visual Studio 2005 Command Prompt Window and went from the configure >> phase right through to build and test. Everything worked beautifully. >> All modules were built and all the tests passed successfully. >> >> As I said, I hope this helps others and, if appropriate, the developers >> might want to state the Microsoft SDK is a requirement for Visual Studio >> builds. >> >> 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. > > -- > Thomas Hruska > Shining Light Productions > > Home of BMP2AVI and Win32 OpenSSL. > http://www.slproweb.com/ > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org > > -- View this message in context: http://old.nabble.com/Successfully-building-openssl-1.0.1-with-Microsoft-Visual-Studio.-tp33558980p34043827.html Sent from the OpenSSL - User mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
