谁有OPENSSL的VC6工程文件?

[yuechuan]

我很想问一下,为啥是要利用perl来完成编译呢?
我现在因为要移植openssl,所以想自己完成源代码的编译,而不是利用现成的库文件
自己尝试编译了一下,出现一堆ERROR
网上好像有现成的工程文件的,但是我没找到,有几个连接还是坏的
大家谁有,麻烦发我一下,谢谢
[e-mail]

[yuechuan]

楼上什么意思? 我的意思是说,我想在自己的工程中直接使用源代码编译,而不是用编译出来OPENSSL的动态链接库

[na_he]

不太明白意思

[yuechuan]

就是不用DLL和LIB呀

[blackcat242]

这个跟vc6有什么关系？
你要看下编译的条件，把库文件都找全了，有点麻烦

[yuechuan]

[Quote=引用 5 楼 unsigned 的回复:]
引用 2 楼 yuechuan 的回复:
楼上什么意思? 我的意思是说,我想在自己的工程中直接使用源代码编译,而不是用编译出来OPENSSL的动态链接库

那你编译成静态库,不就好了?全部添加进工程当中并不合适,这样子会让你每次编译都花费大量的时间,并且不利于升级和维护.

在执行完perl Configure VC-WIN32之后,会在ms目录下生成两个makefile，一个是ntdll.mak，这是动态库的版本，另一个是nt.mak，这是静态库的版本。
[/Quote]

额,是这样的,想把这个东西弄到嵌入式系统中,不是WINDOWS或者Linux的系统.不过想首先在VC上作试验看下
干了一天,还剩下1个Link error...唉..痛苦..

[僵哥]

[Quote=引用 2 楼 yuechuan 的回复:]
楼上什么意思? 我的意思是说,我想在自己的工程中直接使用源代码编译,而不是用编译出来OPENSSL的动态链接库
[/Quote]
那你编译成静态库,不就好了?全部添加进工程当中并不合适,这样子会让你每次编译都花费大量的时间,并且不利于升级和维护.

在执行完perl Configure VC-WIN32之后,会在ms目录下生成两个makefile，一个是ntdll.mak，这是动态库的版本，另一个是nt.mak，这是静态库的版本。

[僵哥]

在Install.W32的说明当中是这样子写的

引用

Visual C++
----------

If you want to compile in the assembly language routines with Visual C++ then
you will need an assembler. This is worth doing because it will result in
faster code: for example it will typically result in a 2 times speedup in the
RSA routines. Currently the following assemblers are supported:

* Microsoft MASM (aka "ml")
* Free Netwide Assembler NASM.

MASM is distributed with most versions of VC++. For the versions where it is
not included in VC++, it is also distributed with some Microsoft DDKs, for
example the Windows NT 4.0 DDK and the Windows 98 DDK. If you do not have
either of these DDKs then you can just download the binaries for the Windows
98 DDK and extract and rename the two files XXXXXml.exe and XXXXXml.err, to
ml.exe and ml.err and install somewhere on your PATH. Both DDKs can be
downloaded from the Microsoft developers site www.msdn.com.

NASM is freely available. Version 0.98 was used during testing: other versions
may also work. It is available from many places, see for example:
http://www.kernel.org/pub/software/devel/nasm/binaries/win32/
The NASM binary nasmw.exe needs to be installed anywhere on your PATH.

Firstly you should run Configure:

> perl Configure VC-WIN32 --prefix=c:/some/openssl/dir

Where the prefix argument specifies where OpenSSL will be installed to.

Next you need to build the Makefiles and optionally the assembly language
files:

- If you are using MASM then run:

> ms\do_masm

- If you are using NASM then run:

> ms\do_nasm

- If you don't want to use the assembly language files at all then run:

> ms\do_ms

If you get errors about things not having numbers assigned then check the
troubleshooting section: you probably won't be able to compile it as it
stands.

Then from the VC++ environment at a prompt do:

> nmake -f ms\ntdll.mak

If all is well it should compile and you will have some DLLs and executables
in out32dll. If you want to try the tests then do:

> nmake -f ms\ntdll.mak test


To install OpenSSL to the specified location do:

> nmake -f ms\ntdll.mak install

Tweaks:

There are various changes you can make to the Win32 compile environment. By
default the library is not compiled with debugging symbols. If you add 'debug'
to the mk1mf.pl lines in the do_* batch file then debugging symbols will be
compiled in. Note that mk1mf.pl expects the platform to be the last argument
on the command line, so 'debug' must appear before that, as all other options.


By default in 0.9.8 OpenSSL will compile builtin ENGINES into the libeay32.dll
shared library. If you specify the "no-static-engine" option on the command
line to Configure the shared library build (ms\ntdll.mak) will compile the
engines as separate DLLs.

The default Win32 environment is to leave out any Windows NT specific
features.

If you want to enable the NT specific features of OpenSSL (currently only the
logging BIO) follow the instructions above but call the batch file do_nt.bat
instead of do_ms.bat.

You can also build a static version of the library using the Makefile
ms\nt.mak

[joshuahuangjinghua]

楼主能不能共享下VC工程啊？Thanks！