Remove

Remove

Re: Can OpenSSL be built as static libs?

Yes, Read INSTALL.XX file available with the source. On 8/14/05, Edward Chan <[EMAIL PROTECTED]> wrote: > > > I was wondering if OpenSSL can be built as static libs as I don't want > people to be able to simply replace the dll's with their own. > > Thanks, > Ed __

Re: MSVC Application linked against static openssl libs is crashing

Thanks Brant Thomsen for the reply, My application is actually a Win32 Dynamic-Library with no MFC support. Any other idea? Thanks and regards -- Qadeer Baig On 6/6/05, Brant Thomsen <[EMAIL PROTECTED]> wrote: > I have had problems getting OpenSSL to link correctly if MFC is being us

Re: MSVC Application linked against static openssl libs is crashing

/MT should be used in MSVC while compiling the app which is using openssl libraries, then I have just confirmed that in c/c++ tab of project settings /MT is already spcified (because the dll which I am creating is multithread). I am using MSVC6.0 Any other idea? Thaks and regards, -- Qadeer Baig

MSVC Application linked against static openssl libs is crashing

can I use openssl static libraries in an app developed in MSVC or CodeWarrior so that I do not need to have openssl dlls on the machine? Great thanks in advance, Regards, --- Qadeer Baig __ OpenSSL Project

Re: libeay32.lib giving some link errors while using on Windows

Great thanks Rush! This exercise did solve the problems :-) Now I see that this problem with nt.mak has already been pointed out by "Matyas Majzik" in one of his emails to this group. Thanks and regards, -- Qadeer Baig On 6/1/05, Rush Manbert <[EMAIL PROTECTED]> wrote: >

libeay32.lib giving some link errors while using on Windows

32.lib) referenced from '_bn_mul_words' in tmp32\bn_asm.obj (libeay32.lib) ... -Link Errors End- What I understand of these errors is that linker could not find definitions of following variables/functions in the library: 1. _abort 2. __iob 3. __pctype 4. __err

Re: How to link statically openssl in a dylib

Hi Rush, Your solution has been very helpful. > (2) does the correct thing. It statically links against your version of > libssl.a. It also acts just like it found the library because of a -lssl > on the linker command line. (Only the functions that are required are > pulled into your executable,

Re: How to link statically openssl in a dylib

Thank you Joseph, I also wondered to see ssl libraries in /usr/lib on my machine, when I started using ssl, but before seeing them there I had tried to compile Openssl on my machine so I thought this compilation has placed them there. But still, client says link them statically :( Regards, -- Qad

Re: How to link statically openssl in a dylib

Hi Rush, Thank you very much for your detailed answer, I'll try this solution. Regards, -- Qadeer On 4/27/05, Rush Manbert <[EMAIL PROTECTED]> wrote: > Hi Qadeer, > > I believe you can just statically link the openssl libraries while > creating a dynamic library. Your dynamic library will just

How to link statically openssl in a dylib

Hi, I am using openssl in an application (this application actually is a ".dylib" on Mac OSX). Currently I am linking openssl calls by using "-lssl -lcrypto" linker options. Since this links openssl calls dynamcally therefor I can only use resulting application on the computers where "libssl.dylib