CEGUI (Crazy Eddie's GUI) Forums

Hi, I've got a slight problem with running an directx10 app in release.
It's running beautifully in debug, but as soon as I'm switching to release, it complains about this CEGUIBase_d.dll...

I'm using VS2008 and I've switched the library dependencies to use the non-debug libraries (the ones without "_d" I presume)...
and if I place the dll by the release exe the program asserts on creating a scheme, font, everything, (Expressing: ms_Singleton)

The buildlog is quiet also... no reports about any faults...

Could it be a faulty lib-build?

Anyone have a clue?

Here's the log.. Thanks!

Fixed it! Only needed to rebuild all the libs and dlls. The zipped source code was the only one working, though.
Thanks anyways ^^;

I had this same problem, it is because the release version was built with debug enabled which makes it use the Debug CRT and also makes it load debug dynamic modules by default.

It's like this: CEGUIBase.dll (built with debug) -> Load Expat dynamically: CEGUIExpat_d.dll -> Load dependencies: CEGUIBase_d.dll -> Errors because both release and debug DLL's are in memory.

This just got me too. At least the stock VC9 release libraries are built with the _DEBUG flag enabled. Maybe the 0.7.1 release should be fixed or the download page should get a note like "release mode libraries are unusable, please build from source".

-Matthias

Hi,

I have not looked at the SDKs at this time, though it definitely seems like we messed up quite badly here I'll confirm for sure tomorrow and add a note to the downloads page as suggested. We'll then need to decide whether to do a re-issue or not

CE.

I have confirmed this mistake in both MSVC++ SDKs and have edited the announcement post and the wiki downloads page to indicate the MSVC++ SDKs should not be used for the reasons discussed in this topic.

Thanks for raising the issue guys, and sorry that this one slipped through

CE.

This is odd, when i open the SDK projects for 0.7.1 i see correct settings:



Am i looking at the wrong settings?

I think the issue is/was that we ended up with the output from the "Release with Symbols" configuration overwriting the output from "Release" (because their output has the same name). This is backed up by the presence of the release version pdb files in the SDKs.

The issue of how this happens is related to the discussion we had about premake and it's automatic use of the debug c/c++ runtime when optimisations are disabled (which we have for the "Release with Symbols" config). This lead us to some other discussion about customising premake to allow us to get over that...

I propose we add options in config.lua to control the inclusion of certain configurations - definitely one for "Release with Symbols", maybe one for Static builds also - this way our SDK specific config file can exclude the existence of the "Release with Symbols" build config completely, thus eliminating the possibility of the above scenario (because even with a custom premake executable, we run the risk of shipping an unoptimised release build!).

CE.

Thanks for looking into this and adding the note!