Missing zlib1.dll (v.1.0.0rc)

Rhone · Post by **Rhone** » Wed Feb 16, 2005 9:34 pm

I am trying to update my application to the stable release of ogre 1.0.0 rc. My application now compiles, but when it runs it crashes looking for zlib1.dll. I tried running the precompiled exes for the ogre samples and they bomb with the same error as well. I have no such dll, and to my knowlege ogre is linking with zlib as a static library. So why is it looking for this dll?

Post by **sinbad** » Wed Feb 16, 2005 9:40 pm

It's distributed with both the Dependencies download and the precompiled demos. It's the latest version of zlib which links as a dll by default. If your precompiled demos don't work maybe you deleted or moved it - it's definitely in the archive.

Rhone · Post by **Rhone** » Wed Feb 16, 2005 10:27 pm

Alright, I found it thanks. While I'm at it, I am now encountering another dll link issue. Now my application cannot find the procedure entry point "op_new_vc@MemoryManager@Ogre@@AAEPAXII@Z". It's acting like I have the wrong version of the dll. However, I'm certain this dll was the one produced by my rebuild of the OgreMain project. The same dll works fine with the sample applications.

Sorry if it's a stupid question. Link errors just evade me sometimes.

neocryptek · Post by **neocryptek** » Wed Feb 16, 2005 10:43 pm

Sounds like your trying to link a debug app to a release dll of ogremain.

Debug dll of ogremain was changed to ogremain_d.dll a few versions back, perhaps you havent changed that in your project linker settings?

-N30

Rhone · Post by **Rhone** » Fri Feb 18, 2005 8:42 pm

Well, the debug input .lib for Ogremain is now called Ogremain_d.lib, but the dll is still being exported as Ogremain.dll right? If I rename the Ogremain.dll the application bombs looking for it without the "_d". I noticed, when compiling Ogremain, I received several warnings like this one:

zziplibd.lib(err.obj) : warning LNK4099: PDB 'vc70.pdb' was not found with '..\..\..\Dependencies\lib\Debug\zziplibd.lib' or at 'c:\Ogre3d\OgreMain\lib\Debug\vc70.pdb'; linking object as if no debug info

and similar warnings for freetype219MT_D.lib as well. Is it possible since the compiler is choking on these libs that it is somehow disabling the debugging info for the whole Ogremain.dll causing the final executable to bomb? I'm grasping for straws now. I'm certain that it's a debug app and a debug Ogremain dll. I can run the application outside the compiler and still get the same dll entry error.

Post by **sinbad** » Sat Feb 19, 2005 1:20 pm

Rhone wrote:Well, the debug input .lib for Ogremain is now called Ogremain_d.lib, but the dll is still being exported as Ogremain.dll right?

Wrong. It's called OgreMain_d.dll and is built that way.

I think you're still mixing debug and release mode binaries. Check all your build paths and where you're putting the dlls. Check how the samples do it.