On Wed, Oct 26, 2005, Steffen Pankratz wrote: > On Mon, 24 Oct 2005 17:12:15 +0400 > "Victor B. Wagner" <[EMAIL PROTECTED]> wrote: > > > On 2005.10.21 at 18:45:13 +0200, Steffen Pankratz wrote: > > > now i'm totally confused no shared libs for win32?! > > > is it a bug? > > > > Not for win32. Just for MSVC build. Use mingw32 and you'll get shared > > build with working dynamic engines. And nothing would prevent you from > > linking these dlls into application written in MSVC. > > > > Just use mingw32 for building openssl dlls. > > why shouldn't it be possible to use MSVC to compile openssl (shared and with > dynamic engine support)? > are there any serious reasons? >
There is a separate build system for MSVC. It generates its own Makefile and various other files from the existing Makefiles. It doesn't attempt to completely parse the files or the options use it just does enough to make the VC build work. What this means is that most simple changes to a Makefile (adding new source files) can be handled automatically. More complex changes (adding new directories or sub libraries) requires manual changes to the build system. In this case a whole new mechanism will need to be added to handle the building of shared library ENGINEs automatically. The main reason it isn't there is that no one has got round to it yet. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Funding needed! Details on homepage. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
