CEGUI (Crazy Eddie's GUI) Forums

The thread that CE supplied a link to explains it quite well.

scriptkid, precompiled headers do work under OSX as we use them for OGRE. Linux also supports precompiled headers using gcc 3.4+ but we don't use them yet for CEGUI (or OGRE).

I think the direction ScriptKid is taking on this is the correct one (i.e. OpenGL and wxWidgets). I also agree that OGRE is probably overkill for what we are trying to achieve here.

You are on your own I'm afraid. As CE said none of the core team have access to an OSX machine. If you do work it out feel free to post a patch.

Sounds like a good idea. Go for it

I'm not sure I follow. When you have CEGUI installed, you can use includes like #include <CEGUI/CEGUI.h>.

If you use Linux it's actually $(prefix)/include/CEGUI where $(prefix) defaults to /usr/local.

Also there isn't really any reason why the headers should live under cegui_mk2/include/CEGUI in CVS since it all gets sorted out at install time.

Oops sorry I forgot to email you about this. I setup the cvs module (ceguiaddons) a few days ago and created a NeLRenderer directory within it. You should have write access to that directory. Let me know if you have any questions

In a few days I'm going to be posting a new roadmap. The main change is actually giving priority to the data driven look and having less of an emphasis on creating new widgets. I feel that it is essential to get it up and running as creating new looks seems to be a major sticking point with some use...

I've committed this to the OGRE renderer with a small modification. Thanks!

I was assuming that the freetype issue mentioned would have applied for both 0.2.1 and HEAD. If we can get a definite answer on the search path location we can hopefully release 0.2.1 today. Gotta love long weekends

Thanks for the patch. Could you post the entire source for your sample application and I'll do some tests and see if I can find out what's going on.

There's no reason not to use localtime. I've committed this change. Thanks for spotting it.

hmm... some of those warnings you can ignore, but the freetype issue definitely needs to be fixed before we can release 0.2.1. Also rather than completely disabling Xerces support under OSX is it possible to allow the end user to select which xml library they wish to use (defaulting with Xerces)? I ...

Sounds like you have an overrun somewhere. Have you tried cutting your code back to the essentials and see if you still have the problem.

Out of interest, does this work when using xerces rather than tinyxml?