Hi,
I thought I'd better wade in here also
First a disclaimer - I'm no "license lawyer"; what I state here is just a mixture of my opinion and my interpretation of the licenses. If you're in any real doubt, you might consider the advice of a legal professional.
As I understand it, you must comply with the licenses for all the components that you directly,
or indirectly, use. For CEGUIBase, this is CEGUI itself, PCRE and FreeType2. Which other licenses you need to consider will depend upon which of the other 'modules' you use (such as XML parsers, renderer modules, image codecs and so on - I know you were specific about the ones you use, but I wanted this to be a more general 'advice' on the subject
![Wink ;)](./images/smilies/icon_wink.gif)
).
Ok. So how do you interpret the licenses? Some things, like FreeType2 require some kind of attribution / credit. So you'd perhaps include a line such as:
The Freetype 2 Font Engine
Portions of this software are copyright © 2008 The FreeType Project
(
www.freetype.org). All rights reserved.
Most of the licenses for most of the libs we use are pretty short and clear - they're kind of MIT / BSD style things where you need to include a copyright notice, a list of three or four 'conditions' and a disclaimer.
What I would suggest is to have an 'acknowledgements' page, either as part of the 'credits' in the app itself, or as part of the documentation (either is acceptable as I understand things. For example, in the binary CELayoutEditor for the Mac, I included an acknowledgements.txt file that attempts to cover all the bases for that particular build/config of the app).
So to summarise / reiterate a little, you need to comply with the licenses for all components you use directly or indirectly.
If I've confused things, I apologise - let me know and I'll have another attempt.
CE.