CEGUI (Crazy Eddie's GUI) Forums

Hey, I'm new to CEGUI and am trying to compile it with Irrlicht 1.6 using MSVS on Windows.

When I try to compile most things go good but I get several errors like this:


What I am assuming is that 0.7 was made before Irrlicht 1.6 was finalized (judging by release dates) and something changed in the irr::io::IReadFile to make getFileName return "const io::path&" instead of "const irr::core::string<irr::c16>&" and they removed c16.

The following seems to fixes the problems (Once I get pcre so I can actually compile I can confirm it works)

In CEGUIIrrlichtMemeoryFile.h
replace

with


replace

with


And in CEGUIIrrlichtMemoryFile.cpp
replace

with


This GUI system looks awesome and I hope to be using it a lot in the future!

~DtD

Hi,

Thanks for the heads up that 1.6 support is broken; I'd seen the release had been made, but did not have a chance to test. These issues will be fixed later on today

[Edit]
With regards to PCRE, if you're using VS 7.1, 8 (SP1), or 9, I point you in the direction of our precompiled dependency packs (linked to in the release announcement posts).

CE.

Thank you very much for your reply,
Yeah, I ended up getting the dependency package. I got CEGUI to compile but I get a ton of "libcmtd.lib(dbgheap.obj) : error LNK2005: __CrtSetCheckCount already defined in MSVCRTD.lib(MSVCR90D.dll)" type errors. Other topics on the forums haven't been able to solve it. Still looking into things.

Ooops, I was compiling CEGUI with Debug and the Samples with Debug_Static. That seems to have fixed that. Then I got a link error consistent with using a Irrlicht Static Lib without _IRR_STATIC_LIB_ defined. So I defined that now the CEGUISampleHelper project gets a ton of thoose libcmtd.lib errors as well as one from irrlicht's lib:

"irrlicht.lib(Irrlicht.obj) : error LNK2005: _DllMain@12 already defined in MSVCRTD.lib(dllmain.obj)"
There is also: "LINK : fatal error LNK1104: cannot open file 'd3dx9.lib'" at the very button.

I'm gonna keep trying to fix it, but if you notice something let me know!

~DtD
PS> CEGUISampleHelper compiled successfully before I fixed the debug, debug static switchout thing.

Ok, I switched out my self-compiled Static Irrlicht for the Dynamic Vanilla one and I cleaned the solution and it compiled everything.
Except it seems I compiled CEGUI without FreeType, so none of the samples run. DOH >.<
Hopefully it was the clean that fixed it, not the dynamic Irrlicht because I'd like to make everything static eventually.

Awesome, recompiled with FreeType and it seems to be 99% working. It was using OpenGL with Irrlicht by default, but I don't have OpenGL drivers so I recompiled again with DX9, and it looks good.

Also, it seems I found a bug. In Sample_TextDemo if you type something in the multiline (EG: "0169") and then backspace it deletes the 9 and jumps over the 6. Then the cursor is between 1 and 6 instead of at the end.

~DtD
BTW> In case you were wondering, I don't have OpenGL drivers because ATI stoppped supporting my graphics card and thier old Vista drivers do not work in Win7.

Hi,

The whole static / dynamic thing is a PITA, and depending on the exact code you're using things are dealt with differently. I'll save you the long version, but basically:

- Releases up to and including 0.7.0 used the wrong c/c++ runtime setting for static builds (the /MD and /MDd options instead of /MT and /MTd).
- The 0.7.x dependency packs contain a single version of the dependency libs, also built with the /MD and /MDd options.
- The CEGUI situation was fixed in the v0-7 branch a couple of weeks ago, though required matching dependency binaries, which were made available yesterday (the 0.7.x-r1 versions).

So basically, it's required to ensure that all components are built with the same runtime setting. For the current v0-7 code and future releases, this will be /MD and /MDd for dynamic builds and /MT and /MTd for static builds (since these are the most likely configurations people will be using). Failure to do this will create many linking issues, and also subsequent runtime issues if (or when) memory gets released across module boundaries.

I'll look into the editbox thing tomorrow

CE.

Ah, ok. Thanks, I will look into that!

I am also going to look into getting CEGUI to use IrrXML (Built in to Irrlicht, but can be used stand-alone) for XML phrasing, and maybe getting it to use Irrlicht's image loader. The only dependency left over would be PCRE which I honestly don't need anyway except for the spinner widgets.

Have you thought instead of using regex for the spinner widget that it might be easier to just check the input as it comes in if all the character(s) are numbers or a decimal? Regex just seems like overkill for something like that.

~DtD

With regards to image loading, so long as you're setting things up correctly this will already be using Irrlicht for the loading - if the log is reporting anything else as the ImageCodec (such as SILLY), then you're not initialising the system in such a way that it will use the integrated Irrlicht image codec. You can either create that yourself via a static call on the IrrluchtRenderer and pass it to the System::create function, or for most purposes can get the system to do it for you by way of the IrrlichtRenderer::bootstrapSystem function. Though note there is an outstanding bug as regards to the cleanup of the Irrlicht and Ogre integrated codecs when linking statically (will be fixed tomorrow).

With regards to the spinner and the use of regex, this is solely because the spinner is not a 'whole new widget' - but rather an Editbox instance with a couple of buttons stuck on the end. With 0.7.0, I've put in place the beginnings of the required mechanism to replace PCRE with other alternatives (so a lightweight, custom alternative would be possible), though this facility is not exposed to the user at this point in time.

CE.

Thank you very much for your help! I tried compiling CEGUI without SILLY, but without it there are linker errors:

It works with the SILLY codec compiled in though.

I got the new version of CEGUI along with the new dependency package and everything looks good. Also, in OpenGL with Irrlicht I get blurry windows:
In OpenGL
In DirectX
I don't know if I mentioned this before, but I did not have OpenGL drivers on my system when I was first trying CEGUI, but I do now so I don't think that'd be the problem. Also, I should note that the examples work fine in OpenGL on my laptop. I made sure all the ATI enhancements were off on my desktop.

My log: (From desktop)

The whole log is here

My desktop:

My laptop:


Also, this isn't so important, but CEGUI does not seem to like the Burning's Video Render in Irrlicht:
(Just shows a black screen, atleast in Demo7, FlaggardDemo, and FontDemo)

~DtD

I tried to set up CEGUI with Irrlicht today. My program hangs and then crashes. I run the start function after I run the irrlicht start function. (otherwise I just get a segfault)

I used these eight win32 lib and dll files:
CEGUIBase.dll /lib
CEGUIExpatParser.dll /lib
CEGUIFalagardWRBase.dll / lib
CEGUIIrrlichtRenderer.dll /lib

My header, and one called function that hangs and then crashes:




The MSVC+ 2008 Express Edition compile command:

/OUT:"Debug/IrrlichtWrapper.dll" /INCREMENTAL /NOLOGO /DLL /MANIFEST /MANIFESTFILE:"Debug\IrrlichtWrapper.dll.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEF:".\IrrlichtWrapper.def" /DEBUG /PDB:"c:\se\oldstuff\IrrlichtWrapper\IrrlichtWrapper_source\Debug\IrrlichtWrapper.pdb" /SUBSYSTEM:WINDOWS /DYNAMICBASE:NO /IMPLIB:"Debug/IrrlichtWrapper.lib" /MACHINE:X86 /ERRORREPORT:PROMPT .\irrlicht-1.7\lib\Win32-visualstudio\irrlicht.lib .\cegui\CEGUIBase.lib .\cegui\CEGUIIrrlichtRenderer.lib .\cegui\CEGUIFalagardWRBase.lib .\cegui\CEGUIExpatParser.lib

What does 'it crashes' mean? As programmers we generally need more information to go on than that.

From the little information given it seems you're linking the release version libs to a debug build. As I mentioned (twice, I think) in IRC last evening, you must ensure you link the debug versions (with the _d suffix) for the debug configuration of the project - this is absolutely essential, otherwise the C/C++ runtime used will not match.

CE.

I switched to debug dlls and here is the error I get:

"Run-Time Check Failure #0: The value of ESP was not properly saved across a function call. This is usually the result of calling a function declared with one calling convention with a function pointer declared with a different calling convention."

I should note I am using the latest irrlicht, 1.7.1.

Edit: Here's the current compile command:

/Od /I ".\irrlicht-1.7\include" /I ".\irrlicht-1.7\source\Irrlicht" /I ".\cegui\include" /D "WIN32" /D "_WINDOWS" /D "_DEBUG" /D "_USRDLL" /D "_VC80_UPGRADE=0x0710" /D "_WINDLL" /D "_AFXDLL" /D "_MBCS" /Gm /EHsc /RTCu /MDd /Fo"Debug\\" /Fd"Debug\vc90.pdb" /W3 /nologo /c /Wp64 /TP /errorReport:prompt

I didn't see your previous message, but I answered it. (I have ESP)

Using all debug, no-go.

Actually I'm extremely depressed right now that it crashes.

Very, very depressed...

More info:

* I am using MSVC 2008 Express Edition.
* I traced the crash to this function inside ceguiirrlichtrenderer.cpp:



Device initialization code:

Ok. Ok. I tried compiling cegui.

I have 5 errors when I try compiling the irrlicht renderer!!

The particular assertion you're getting indicates one of two main possibilities. First, is that there is some conflict between calling conventions being used for some function, and second, is something is corrupting the stack somewhere.

Generally, if the assertion gets raised at the same point every time in every run, then it might indicate that it's a calling convention issues - but does not rule out stack corruption from elsewhere. If the assertion is raised at different times, and perhaps at random points in the code, then this is more indicative of stack corruption and we could be confident in ruling out calling convention issues.

Given the point where you indicate the assertion gets raised, I would say it could be a calling convention issues as regards to the Irrlicht lib. Can't be 100% sure though, these things are always somewhat difficult to diagnose and debug across the Internets.

With regards to the later compile issues, this is likely because the Irrlicht SDK version specified in the config.lua file is set incorrectly - probably at 14, whereas it should be set to 16.

HTH

CE.

With those changes to the lua script, I was able to compile "CEGUIBase" and "CEGUIIrrlichtRenderer" lib/dll files with Irrlicht 1.7.1 with MSVC++ 2008 EE.

They have a different file size from the SDK version.

The function with the bootstrap code now runs with no error. Thank you.