Problems encountered during ice Development (3)

Today I tried to writeProgramCopy to the test machine and run it. The error window is displayed, indicating that the configuration is incorrect and the task cannot run.

I almost had to crash. Previously, I used vc6.0 to copy a msvc60.dll and it was okay. I compiled it with vs2008, except for running on my own machine, several other machines cannot run.

So download redist everywhere. MSC, the result is useless, and then use depend to view the dependent DLL, and find that my program is in the debug version, so the dependent DLL suffix has a D, so find this directory: c: \ Program Files \ Microsoft Visual Studio 9.0 \ Vc \ redist \ debug_nonredist \ x86

Run the following c: \ Program Files \ Microsoft Visual Studio 9.0 \ Vc \ redist \ debug_nonredist \ x86 \ microsoft. vc90.debugcrt

C: \ Program Files \ Microsoft Visual Studio 9.0 \ Vc \ redist \ debug_nonredist \ x86 \ microsoft. vc90.debugmfc

The DLL files in these two directories are copied to the test machine, and the configuration error is no longer displayed.

 

But the error persists. ice34.dll is missing. This is easy to understand. Go to c: \ ice-3.4.0 \ CPP \ bin and find all the dependent DLL copies to run the program.

However, an error window is displayed.

Pluginmanageri. cpp: 326: ice: plugininitializationexception:
Plugin initialization failed: Unable to load entry point 'icessl: createicessl'

Baidu went back to the zeroc forum and read several related posts, saying that the SSL path conflicts. Different versions are used. SSL mainly uses libeay32.dll and ssleay32.dll, there may be different versions of ssl dll in Windows/system32.

For details, see here:

Http://www.zeroc.com/forums/help-center/4028-problem-hello-demo.html

 

But I found my c: \ windows \ system32, or even the entire computer, and did not find the second libeay32.dll.

When I was desperate, I suddenly found two icessl34.dll and icessl. dll under c: \ ice-3.4.0 \ CPP \ bin. Will this be the SSL required by ice. So I copied the two DLL files to the target machine and finally did not see the annoying alarm. My lovely program interface finally came out.