|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
Some portions of Crystal Space are not covered by LGPL license. You might have to consider this, depending on how you intend to distribute your finished product. However, this is usually not problematic, as the modular design of Crystal Space allows to simply exclude the components in question.
Licensed under the GNU General Public License. See section GNU General Public License.
In addition, some components may need to link to external libraries covered under a license other than the LGPL.
Crystal Space contains facilities to aid in the debugging and developing of both the engine and client products; one of those is the ability to create call stacks. On MinGW, in order to obtain meaningful symbol names for call stacks, the BFD library is used, which is licensed under the GNU General Public License (see section GNU General Public License).
Call stacks are provided by the very core of Crystal Space, this means that any plugin or application linking against Crystal Space also links against BFD. However, since this facility is only sensible for debug builds, BFD is only used by “debug” builds, not “profile” or “optimize” builds.
As linking against BFD “infects” a project with the GPL, you need
to be careful when shipping debug builds compiled on MinGW if you use a license
that is not GPL-compatible. You can avert such problems by disabling the
use of BFD; this is done by passing
--without-bfd as a parameter to
configure. Again, note that this only affects debug builds on MinGW;
optimize builds or builds on any other platform are by default “safe” as they
won't use BFD.
This document was generated using texi2html 1.76.