Win32 build broken

2003-03-29 Thread Gisle Vanem
Looks like the build for all Win32 targets (MSVC, MingW)
got broken with the introduction of the ./engines directory.

I looked at it, but failed to see where the dir is included. 
Please, someone with more knowledge fix this.

--gv

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]


Re: Win32 build broken

2003-03-29 Thread Robert Allerstorfer
Hi,

I built the latest 0.9.7b-dev snapshot successfully under Win32, using
the 'no-engine' configuration option. The Unix-like build system with
the 'mingw' target - as introduced in 0.9.7b - didn't accept 'shared',
though. The Configure script complained with

You gave the option 'shared'.  Normally, that would give you shared libraries.
Unfortunately, the OpenSSL configuration doesn't include shared library support
for this platform yet, so it will pretend you gave the option 'no-shared'.  If
you can inform the developpers ([EMAIL PROTECTED]) how to support shared
libraries on this platform, they will at least look at it and try their best
(but please first make sure you have tried with a current version of
OpenSSL).

But, I was able to build the shared object files (libeay32.dll and
libssl32.dll) using the old-style ms\mingw32 method. Anyone got an
idea on how to enable 'shared' support for MSYS based Win32 builds?

best,

rob.

--
On Sat, 29 Mar 2003, 16:24 GMT+01 (16:24 local time) Gisle Vanem
wrote:

 Looks like the build for all Win32 targets (MSVC, MingW)
 got broken with the introduction of the ./engines directory.

 I looked at it, but failed to see where the dir is included. 
 Please, someone with more knowledge fix this.

 --gv


__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]