• <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 楊粼波 閱讀(529) 評論(0)  編輯 收藏 引用

            色婷婷综合久久久久中文一区二区| 久久久WWW成人免费精品| 久久久精品波多野结衣| 国产精品久久久久影院色| 久久青青草原亚洲av无码app | 国产精品久久久久久福利69堂| 欧美黑人激情性久久| 亚洲va久久久久| 日本五月天婷久久网站| 久久精品亚洲AV久久久无码| 亚洲精品成人网久久久久久| 久久这里只有精品首页| 色偷偷偷久久伊人大杳蕉| 精品久久久久久久无码| 精品午夜久久福利大片| 精品久久久久中文字| 欧美性大战久久久久久| 久久久久亚洲精品日久生情| 久久婷婷激情综合色综合俺也去| 精品少妇人妻av无码久久| 久久精品国产精品亚洲精品| 婷婷久久综合九色综合98| 深夜久久AAAAA级毛片免费看| 久久亚洲国产精品成人AV秋霞| 久久精品无码午夜福利理论片| 久久亚洲国产精品一区二区| 久久久精品视频免费观看| 亚洲精品乱码久久久久久不卡| 麻豆成人久久精品二区三区免费| 91秦先生久久久久久久| 一级做a爰片久久毛片免费陪| 久久成人国产精品| 亚洲国产香蕉人人爽成AV片久久| 久久久久久精品成人免费图片| 久久精品这里热有精品| 欧美精品乱码99久久蜜桃| 久久综合久久久| 日产精品久久久一区二区| 久久精品不卡| 久久免费高清视频| 一本色道久久88—综合亚洲精品|