CEGUI (Crazy Eddie's GUI) Forums

EDIT: This is my second typing of this rather long message. The forum software errored out on me when I hit submit. I hope I don't leave anything out on this retype.

I am at my wits end here. I've been wrestling with this one for the last few days and nothing seems to solve it. I know there are people using Ogre 1.7 and CEGUI 0.7.1 successfully so I know it is possible.

First, yes, I have searched these forums, the ogre forums and the web in general for a solution. Nothing I found worked.

Here is my setup:
Ogre 1.7 (from source)
Ogre 1.7 dependencies (compiled from source)
CEGUI 0.7.1 (from source)
CEGUI 0.7.1 precompiled depenendencies (for v9)

I am using Visual C++ 2008 Express on a Windows XP Professional installation.

Here is the issue. I have compiled Ogre 1.7 and it runs correctly before even trying to add CEGUIbase_d.dll.

As soon as I add in CEGUIbase_d.dll into the mix my application will cease to initialize. The report stating:



It appears to be the classic missing ATL security fix issue. However, upon looking at my VC++ 2008 express installation, it says I have sp1 and a few other updates.

Still I downloaded the ATL fix file(s) and after 6 hours of downloading it tells me that the patch does not apply. Imagine my frustration at that.

I tried the redistributable package too but that also does not apply. I suspect it is because it already exists on my system.

The only other solutions I saw were to download and recompile all the CEGUI dependencies (which didn't work) and to get VS 2005 and recompile everything (which is as silly as fixing your car by buying a new one).

What am I missing here? I have probably made some minor mistake that will be obvious to everyone else and make me feel stupid but since I am not seeing it I seem to have exhausted my options.

Because you're building from source you should not be getting any issues at all (yeah, stating the obvious, I know).

It seems to me that it's just a case that the manifest embedding may have failed for the DLL - I see this fairly frequently when I have to use MSVC++. Are you able to manually inspect the manifest in the DLL with the manifest tool (mt.exe)? What happens if you just hit build again for CEGUI, and recopy the DLL file(s)?

Sorry I have not been able to give a definitive answer, though it seems it's going to be something really silly, like the above

CE.

Using mt.exe to verify the manifest came out good. I'll try forcing a rebuild of CEGUIBase since the compiler thinks its all ok (except when I try to add it to OGRE).

I'm an old school computer scientists, from when we programmed assembly language one byte at a time if we had to. We didn't have no fancy manifests back then.

Thanks, I'll continue to dig into this as its holding me up right now.

During the recompile I see:


I wonder if that has anything to do with the issue. They are warnings so I tend to ignore them.

Also later on I find a series of :



Which seems to indicate that the precompiled dependencies were using vc8 instead of 9. At this point, I am just guessing, though.

Well nuts. After recompiling I still have the same issue.

EDIT: I realize this is becoming quite long but I wanted to post what I am doing in case it helps someone else.

I have been chasing down this side by side problem.

BTW- you can get better info from examing the event log viewer under system (when using xp or vista). It will tell you what is really missing.

In my case I get :


You can then look in Windows/WinSxs and see if a directory with that name exists or not. In my case, I do not have a VC80.DebugCRT because I don't have VC80 installed. Further, there is no redistributable of the VC80 debug CRT.

It is probably no accident that in my research I have found the words Hell and Manifest used in the same sentence.

Given that it is apparent that something in CEGUIBase_d.dll (and likely CEGUIBase.dll) was looking for vc80.pdb as shown above, I am suspecting that freetype_D.lib is the culprit. I will edit this post when I find out one way or another.

The vc80 Debug CRT requirement explains why installing VC2005 worked for people.

Ok, for the grand solution.

I had two copies of the dependencies in my download directory and apparently had unzipped the vc 2005 zip file and not the vc 2008 zip file.

Thus all the dependencies having trouble finding the vc80.pdb and their inexplicable desire to find the vc 80 debug crt.

So, there it is, the silly minor thing that will make me feel stupid.

hehe Glad you figured it out.

CE.