> >By the way, I downloaded and tried that build for C++Builder 5 today > >(I'm running XP). Perhaps I didn't install it correcty, but I overlaid > >the 2 .lib's on top of the one's I had built from the source and were > >already included in my project, etc. However, my app crashed with > >access violations when I tried to run with the pre-builds. I had to > >rebuild from the source again to restore those 2 libs and all was ok > >again. > > > >I can do some additional testing if anyone from that project wishes > >it. > > That's really weird. You are the second person to say that you have > problems with Builder 5 working with Win32 OpenSSL. I've got Builder 5 > Enterprise and have no problems with it working with Win32 OpenSSL 0.9.7c > (ProtoNova is compiled with Builder 5 and I haven't had any exceptions > raised). > > What version of OpenSSL are you running with?
0.9.7c > Do you have the latest patches for Builder 5? No, my install is right off the original C++Builder 5 distrib CD (Build 12.34) > Did you try 'implib' on the pre-built DLLs (does that fix the problem)? Um. No. What's implib? :) I am new to the C++Builder environment. I had used MSVC several years ago (v 1.5 ad 2). I've spent the last several years in C on Linux however, so I'm still coming back up to speed in Windows programming. > Did you copy the contents of the 'include' directory to your Borland > installation (I doubt that this would fix anything, but just to cover that > bases)? Yes, I did. I copied them to borland's /include under /openssl from there. > Did you try re-building your entire project? Yes. > Where were the access violations? I forget. I will have to install it again and test for this. > Are you using command-line or GUI mode? GUI mode. > VCL or no? Yes, I have some VCL components in my app, and have included vcl.h > Are you able to step through with a debugger to the point of failure? > Can I get some sample source code that causes the problems to occur? I'l have to install it again and try this as well. > Does your code compile with MSVC, if so, does it still raise > an exception? My latest version of MSVC is vers 2 and I wasn't considering even trying that one. > Technically, there should nothing wrong with the DLLs. They > are just like every other DLL on the system with exports, etc. (and they > are built with MSVC++). However, I wans't tryiing to use the dlls. I copied the 2 .lib files to Borlands /Lib directory and have those included in the project. Should I not use the lib files? Thanks, Dann ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
