CEGUI (Crazy Eddie's GUI) Forums

Hi,

I am not sure it is fully relevant, but an issue for me was to tell the CEGUI library where to find the various resources it relies on (ex: 'defaultResProvider.setResourceGroupDirectory("schemes",..' etc. for imagesets, fonts, layouts, etc.).

As the library I am integrating CEGUI into, like the CEGUI itself, can be installed in a user-specified location, I had to tell the integrating library what CEGUI's base path was to be used for resources (either as a configure-generated symbol in a file, or thanks to the -D preprocessor option and some macro hack to protect this path).

I did it but it was not very straightforward; I was wondering if something simpler/cleaner could be done.

I was thinking that a function like const std::string & CEGUI::GetDefaultInstallBaseResourceDirectory() would be ideal from the users' point of view (it would for example return "/home/joe/my-CEGUI-0.7.5-install/share/CEGUI"). It could be possible to implement, provided one does not override the install target (specified at configure-time) once CEGUI has been built.

Another option would be to generate a config script that would set all compile and link settings for the users, a bit like SDL does it:



CEGUI's counterpart could then add a -DCEGUI_RSC_PATH="/home/joe/Projects/CEGUI-0.7.5/share/CEGUI" for example.

Would it make sense? Is there any better solution for that resource path issue?

Thanks in advance for any hint,

Olivier Boudeville.

the resourceGroups are not part of a library, u have to set them manually

you should look at this tutorial:

[url]
http://www.cegui.org.uk/wiki/index.php/ ... rce_Groups[/url]

you should put everything you need in to a sub directory of your Project's directory and then use relativ Path names, so it can be found after installation.

some example shemes, layouts etc can be found in the datafiles directory.

I hope this helps

I don't think that a default path make seens cause Users want to put their files where they need them and ship them with their applkication

Hi,

Yes, one could copy locally datafiles and refer to them with relative paths. I thought that pointing directly to installed CEGUI's built-in ones (ex: for the Taharez look) could be cleaner (no duplication among user's data, and a single version can be shared between all CEGUI-using apps) and safer (w.r.t. licensing, but apparently this is a non-issue in most cases), but indeed there is little interest in that. It all boils down to considering whether this data is part of CEGUI or not!

And anyway, later, I will consider reading this data not directly from the filesystem, but from an abstract one (PhysicsFS), unless it raises too much difficulties. Time will tell!

Thanks for your answer,

Olivier.