OpenSSL-0.9.5 MS Visual C++ Project files Available
If you're not using Windows NT, 95 or 2000 you can delete this now.
For 0.9.5 - http://www.iconsinc.com/~agray/ossldev/
I only have VC6 for right now - will put out vc5 when i find my cd.
Even though i write the project files by hand - I still like to
double check.
I've had this for a week or so, but wanted to wait for all of the
relevent bugs to be fixed within the openssl development tree.
Please follow the readme to the letter especially step 3 below - else
you'll have lots of errors and warnings. Otherwise everything builds
without warnings or errors and all tests pass.
Regards,
Andrew Gray
*************Release notes/ Readme*************
Developer Studio Workspace and Project files for openssl-0.9.5
Installation:
1. Extract openssl-0.9.5.tar.gz as you normally would.
2. Extract VC6ossl095.zip targetting the openssl-0.9.5 (or whatever name it's in)
directory. This will create another directory named "msvc" at the top
of the SSLeay directory tree.
3. Open a command prompt and run "perl Configure VC-WIN32" as per the
instructions in the $openssl-0.9.5_ROOT/Install.w32 file. Then run "ms\do_ms.bat"
VERY IMPORTANT - BEFORE CONTINUING
THERE ARE SEVERAL BUGS IN THE OPENSSL-0.9.5 RELEASE THAT PREVENT A FULL BUILD OF
INDIVIDUAL
EXECUTABLES. These have been fixed within the cvs tree so if you are using a snapshot
or a draw off of the openssl cvs tree dated after 5 March 2000 you can skip these fixes
For the 0.9.5 release though, these need to be fixed before continuing to step 4.
BUG1:In crypto/rand/rand.h replace line 93:
#ifdef WINDOWS
with
#if defined(WINDOWS) || defined(WIN32)
BUG2:In apps/app_rand.c replace line 112
#include "apps.h"
with
#define NON_MAIN
#include "apps.h"
#undef NON_MAIN
BUG3:In apps/spkac.c add in the following within the include block
at the top of the file:
#include <openssl/lhash.h>
#include <openssl/conf.h>
note:these changes do not affect the ability to build from the default command
line instruction - nmake ms\ntdll.mak
4. Return to your command prompt and from the openssl root directory run:
"perl msvc\doinc.pl" This is a quick hack that creates the output
directories and copies the header files much as what ntdll.mak does at
the start of a command linebuild. All of the dependencies for header
file locations are built into the developer studio workspace.
5. Open the developer studio workspace - openssl-0.9.5\msvc\openssl.dsw
This will open up a Microsoft Developer Studio Workspace containing 50
or so projects. Dependancies are built into the workspace -
i.e. libeay32.dll will be built automatically before asn1parse.
Executables are both built independently and also as openssl.exe.
6. It's best to do a "batch build" first. Menu:Build/Batch
Build... And build both the release and debug builds for everything -
If any errors arise then .....->
Things that typically cause errors:
1.Make sure that ALL Microsoft SDKs are removed from your default include path in
Menu:Tools/Options | Directories.
2.Not Running configure or ms/do_ms.bat in step 3.
Other things:
This has been built using NT4 sp5, with VC++ 6.
The default c runtime for all debug workspaces is Debug Multithreaded dll. For
the Release build it is Multithreaded dll. If you change it - What ever you
do don't mix it across projects - that is make sure its consistent across everything...
I dump everything into out32dll/Debug for the debug build. It goes into
out32dll/Release for the release build. If either directory doesn't exist, it
will be created on the first build. This can be changed in the Project Settings tab.
In a cursory run through - all the tests listed above succeed. You'll have to twiddle
the default ssleay.cnf file for testing for stuff like req, ca , etc, but they all
seem to work.
I've left the precompiled header flags on - even though they consistently get
regenerated, it does tend to speed things up (I think).
RSAREF stuff is not included
Oh yea- this stuff is hereby put into the public domain but if you use it dont forget
that all the source files which it wraps are Erics and Tims:
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
* 4. If you include any Windows specific code (or a derivative thereof) from
* the apps directory (application code) you must include an acknowledgement:
* "This product includes software written by Tim Hudson ([EMAIL PROTECTED])"
and of course:
lots of it is Copyright (c) 1998-2000 The OpenSSL Project. All rights reserved.
And if you end up really using it alot, buy me a beer if you ever run into me :-)
The Microsoft Developer Studio Packages for Visual C++ v. 6 can be
found here for Openssl-0.9.5. - http://www.iconsinc.com/~agray/ossldev/
Openssl0.9.4 packages for VC++ 5 and 6 are here -
http://www.iconsinc.com/~agray/ossldev/old/
Contact me directly for SSLeay packages from 0.6.0 onwards - but you
really should upgrade.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
