Release Notes

The web page documentation is continually updated, so for the most recent information check the web site, www.grinninglizard.com/kyra, the FAQ, or the discussion boards on SourceForge.

  • Build errors from 'configure' and 'make'. There seems to be some version compatibility issues still in the autotools system. There are 2 solutions if you have problems building:
    1. [On FreeBSD] pkg-add -r libtool; libtoolize --force; ./configure; gmake ;gmake install
    2. [General] make using the "classic" system: make -f MakefileKyra
  • Link errors in Windows VC 6. There are dependencies missing in some windows builds that result in link errors. To work around this, put the encoder.dsp and spriteed.dsp into the same workspace as your engine.dsp. You can drag and drop the dsp files into a workspace to do this, or use "Insert Project Into Workspace" menu option. Then under the Project-->Dependencies menu item, give the encoder and sprite editor a dependency on the engine.
  • Linking to the Kyra library. There are reported problems linking debug code to a release Kyra library and vice versa; this should be cleaned up in 1.4 but hasn't been tested. However, it is very useful to get asserts and errors from Kyra as you develop. I recommend linking to a debug library when debugging and release to release. Also I recommend static linking -- Kyra is not binary compatible between versions, so there is really no point to a dynamic link, unless you can be sure that you get the correct version.
  • 8 Bit Source Images. 256 Color images (notably GIF and PNG) sometime confuse the Sprite Editor, so it will not correctly apply the color key. It comes about because the surface comes back from SDL_image as a 32 bit surface, rather that 8, which confuses the interpreter. If your color keys aren't working with a 256 color, try saving the image as a 24 bit TGA. (The TGA format -- 24 and 32 -- meshes particularly well with Kyra's approach to graphics files.)