Quick bit: I assume your code was using Winsock (WSAxyz()) calls before, NOT going 'through' any obscure MFC TCP communication class which I tried to forget all about by multi-annual liquor medication, right?
Then, second assumption: your binary OpenSSL distro comes with DLLs, so you're 'dynamic library' all around? 'unresolved external' errors are generally from your linker, so that reads to me like all your header files and all thing _compiler_ are in the right place for an initial attempt (won't say if it'll actually work: check your settings (and the ones used to produce those ssl DDLs!) regarding single- vs. multithreaded + debug vs. release run-time library usage. Simple rule when you want to play safe: all DLLs and EXE must have used same settings regarding 'run-time library' in your MS project compiler settings. Now to the linker error you mention: this looks like you did not get - or do not point to the 'right' directory containing - the .lib files that should come with a DLL if you wish to link to it. Compare to Winsock2, which is a Microsoft provided system DLL: when you wish to use it, you include a tiny ws2_32.LIB file in your LINKER 'include' line. If you don't have the .lib files, you have two, sorry, three ways to go: 0) request the .lib files for the DLLs that lack them 1) use run-time dynamic loading: that is: define code wrappers which delay-load the openSSL DLLs. Usually, you only do this kind of thing for OPTIONAL DLLs/code, so I advise against this practice - especially as you'll need to work quite a bit on it as OpenSSL has a large API and you're not done with one call/function there. In short: evade like it's the plague. 2) get a source-based distro and compile the OpenSSL DLLs yourself: the .lib files are a 'by-product' of the DLL linker process. Hope that helps you along, Ger On Tue, Sep 2, 2008 at 5:01 PM, <[EMAIL PROTECTED]> wrote: > > I know that all mailing lists cringe when newbies post. But I'm in a real > bind and so at the risk of putting myself in that category, I have some > basic questions. > > I am using VS 2003 to maintain several MFC applications. These apps > communicate with a web service that recently moved to https://.... So I am > trying to get open ssl into my code. I have downloaded a binary > distribution of the win32 (0.9.8h) and installed it. I have also put open > ssl function calls into my code. It compiles OK, but I get "unresolved > external" errors. I have the compiler configured to "Use MFC in a shared > DLL". Does anyone have any information that will help me get this thing > linked so I can begin learning more about SSL as I attempt to communicate > with my web service? > > Thanks, > Scott Hill > Flying J, Inc. > > Food for thought: > A good pun is it's own reword. > Energizer bunny arrested! Charged with battery! > A pessimist's blood type is always B-negative. > 42.7 percent of all statistics are made up on the spot. > How much deeper would the ocean be without sponges? > Atheism is a non-prophet organization. > -- Met vriendelijke groeten / Best regards, Ger Hobbelt -------------------------------------------------- web: http://www.hobbelt.com/ http://www.hebbut.net/ mail: [EMAIL PROTECTED] mobile: +31-6-11 120 978 -------------------------------------------------- ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
