• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            牽著老婆滿街逛

            嚴以律己,寬以待人. 三思而后行.
            GMail/GTalk: yanglinbo#google.com;
            MSN/Email: tx7do#yahoo.com.cn;
            QQ: 3 0 3 3 9 6 9 2 0 .

            Building OpenSSL for Visual Studio

            轉載自:http://developer.covenanteyes.com/building-openssl-for-visual-studio/

            Building OpenSSL for Visual Studio on Windows is mostly straight-forward, but it has some quirks. I’ll document the results of my wrestling here so that future attempts will be less painful.

            What you need

            You need to install…

            Setting up for the build

            Unzip3 the OpenSSL source code into two different folders, one for the 32-bit build and one for the 64-bit build4. So, for example, you might end up with C:\openssl-src-32 and C:\openssl-src-64.

            Building the 32-bit static libraries

            1. Open the Visual Studio Command Prompt (2010)5.
            2. cd to your OpenSSL source folder for 32-bit (e.g. cd C:\openssl-src-32).
            3. Run the following: 6
            perl Configure VC-WIN32 --prefix=C:\Build-OpenSSL-VC-32
            ms
            \do_ms
            nmake 
            -f ms\nt.mak 
            nmake 
            -f ms\nt.mak install

            Your outputs will be in C:\Build-OpenSSL-VC-32.

            Building the 32-bit static libraries with debug symbols

            These steps will embed the debug symbols directly into the .lib files. Don’t expect to see any .pdb files.

            1. Open the Visual Studio Command Prompt (2010).
            2. cd to your OpenSSL source folder for 32-bit (e.g. cd C:\openssl-src-32).
            3. Run the following:
              perl Configure debug-VC-WIN32 --prefix=C:\Build-OpenSSL-VC-32-dbg
              ms
              \do_ms
            4. In a text editor (like Notepad), open ms\nt.mak and replace all occurrences of /Zi with /Z7. There should be three replacements.7
            5. Run the following:
              nmake -f ms\nt.mak       
              nmake 
              -f ms\nt.mak install

            Your outputs will be in C:\Build-OpenSSL-VC-32-dbg. Make sure you rename them to something likelibeay32-debug.lib and ssleay32-debug.lib.

            Building the 64-bit static libraries

            1. Open the Visual Studio x64 Win64 Command Prompt (2010) (in the Start menu).
            2. cd to your OpenSSL source folder for 64-bit (e.g. cd C:\openssl-src-64).
            3. Run the following:
              perl Configure VC-WIN64A --prefix=C:\Build-OpenSSL-VC-64
              ms
              \do_win64a
              nmake 
              -f ms\nt.mak   
              nmake 
              -f ms\nt.mak install

            Your outputs will be in C:\Build-OpenSSL-VC-64.

            Note: The outputs of the 64-bit build are still named libeay32.lib and ssleay32.lib. You’ll have to rename them more sensibly yourself.

            Building the 64-bit static libraries with debug symbols

            These steps will embed the debug symbols directly into the .lib files. Don’t expect to see any .pdb files.

            1. Open the Visual Studio x64 Win64 Command Prompt (2010).
            2. cd to your OpenSSL source folder for 64-bit (e.g. cd C:\openssl-src-64).
            3. Run the following:
              perl Configure debug-VC-WIN64A --prefix=C:\Build-OpenSSL-VC-64-dbg
              ms
              \do_win64a
            4. In a text editor (like Notepad), open ms\nt.mak and replace all occurrences of /Zi with /Z7 except on the line starting with ASM. There should be two replacements. 8
            5. Run the following:
              nmake -f ms\nt.mak
              nmake 
              -f ms\nt.mak install

            Your outputs will be in C:\Build-OpenSSL-VC-64-dbg. Make sure you rename them to something likelibeay64-debug.lib and ssleay64-debug.lib.

            What not to do

            I tried every method under the sun to get a Windows build of OpenSSL that would link against Visual Studio projects. I learned a great deal along the way. Here’s what I learned not to do:

            • Don’t blindly follow the Windows 32-bit/64-bit installation instructions provided in the OpenSSL source folder. Get guidance online.
            • Don’t build OpenSSL in Cygwin. It’s easy. It won’t link against Visual Studio.
            • Don’t build OpenSSL in MSYS or MinGW. It’s hard. It won’t link against Visual Studio.
            • Don’t try to use NASM like the Windows installation instructions mention. It’s not necessary for Visual Studio builds. (It only supports 32-bit anyway.)
            • Strawberry Perl doesn’t always work in these weird configurations. ActivePerl seemed more stable.
            • Don’t try to build 32-bit and 64-bit OpenSSL in the same folder. The first build will leave artifacts that will mess up the second build. (Running a clean isn’t enough, apparently.)
            • Don’t try to build 32-bit OpenSSL inside of Visual Studio’s 64-bit command prompt and vice versa. It doesn’t work.

            References

            These were very helpful places:

            Footnotes:
            1. Strawberry Perl has been less reliable historically, but I see the comments for success stories.
            2. OpenSSL version 1.0.1c was the latest at the time of writing.
            37-zip is good for unzipping .tar.gz files on Windows. It’s a two-step process.
            4. OpenSSL’s build scripts are not clever enough to handle two different platform builds in sequence. Separate platform builds must start from scratch.
            5. You can find it somewhere in the Start menu.
            6. Using ms\\ntdll.mak will build the shared library instead.
            7. The /Zi option works, but it’s hard to find the right .pdb file without specifying more options. For the sake of simplicity, the /Z7 option just embeds all the debug symbols into the .lib files. Read more here.
            8. For the 64-bit build, Visual Studio uses MASM (ml64.exe) to compile assembly code. According to MASM’s documentation, the /Z7 option is not supported.

            posted on 2016-06-16 18:23 楊粼波 閱讀(530) 評論(0)  編輯 收藏 引用

            亚洲人成无码网站久久99热国产| 亚洲国产成人乱码精品女人久久久不卡| 欧美亚洲国产精品久久| 亚洲另类欧美综合久久图片区| 国产99久久久国产精品小说| 欧美熟妇另类久久久久久不卡 | 久久人人爽人人爽人人片av麻烦| 99久久夜色精品国产网站| 精品人妻久久久久久888| 国产精品99久久久久久www| 久久精品国产99国产精品亚洲| 狠狠色丁香久久综合婷婷| 模特私拍国产精品久久| 精品亚洲综合久久中文字幕| 色婷婷狠狠久久综合五月| 欧美777精品久久久久网| 无码伊人66久久大杳蕉网站谷歌| 久久精品国产亚洲Aⅴ香蕉| 久久丫精品国产亚洲av| 一本色道久久综合| 国产国产成人久久精品| 99久久精品午夜一区二区 | 国产99久久久国产精品小说| 国产成人久久精品麻豆一区| 99re这里只有精品热久久| 亚洲精品无码久久千人斩| 久久久久久久久久久免费精品| 日本道色综合久久影院| 国产Av激情久久无码天堂| 久久精品aⅴ无码中文字字幕重口 久久精品a亚洲国产v高清不卡 | 精品久久久久久亚洲精品| 久久精品国产男包| 少妇被又大又粗又爽毛片久久黑人| 爱做久久久久久| 国产精品亚洲美女久久久| 久久亚洲国产中v天仙www| 欧美一区二区精品久久| 88久久精品无码一区二区毛片 | 久久福利青草精品资源站免费 | 久久九九有精品国产23百花影院| 亚洲精品无码久久久久久|