FIFE community & development blog

Known issues

For some odd reason, Code::Blocks support broke at some point in the past. If you build FIFE with Code::Blocks right now, the build process itself won’t show any problems, but the resulting binary is borked somehow. This needs closer investigation but it’s unlikely that it’s related to the new DevKit. Therefore we can hopefully address the problem with a small fix to the Code::Blocks build template in SVN and don’t have to update the DevKit again to restore proper Code::Blocks support.

Further notes

You’ll need the new Win32 DevKit to build SVN trunk revision 3073 and newer. The old 2008.1-r1 compile SDK will not work with newer revisions anymore!

We furthermore recently changed the default location where the 3rd party dependency DLLs get copied to. They will now reside in FIFE/engine/swigwrappers/python instead of in every single FIFE client directory as it has been in the past. The reason why I changed the path is that Win32 searches for them in the FIFE/engine/swigwrappers/python directory first because that’s where the _fife.pyd binary lies. The old location of the DLLs could lead to DLL clashes as Win32 would search in PATH directories first before looking for them in the FIFE clients directories.

This lead to a problem for one user who tried to get the recent UH release working on his system. The new approach does come with drawbacks, especially as we plan to support C++ game creation with FIFE as well. A new place for the DLLs should be found in the long run but FIFE/engine/swigwrappers/python will do it for now.

The November 2009 DevKit has been a joint effort by FIFE developer Cheesesucker and former FIFE dev mvBarracuda. This said: the November 2009 DevKit will be the last release from my side. I’ve maintained the package for a couple of years and it’s time for me to move on and focus on PARPG. The project is in good hands now so I’m positive that somebody else will update the DevKit in the future when the necessity arises.

Quick and dirty copy and paste install guide from the README:

Installation / build process
===============================
1. Check out the latest engine sources from SVN or update your SVN checkout in case you have already checked out from SVN before:
Repository URL: http://fife.svn.cvsdude.com/engine/trunk

2. Get ActivePython 2.6 and install it to a location of your choice:

http://downloads.activestate.com/ActivePython/windows/2.6/ActivePython-2.6.4.8-win32-x86.msi

3. In case you’ve built FIFE with an older compile SDK in the past, run [FIFE]\build\win32\delete_sdk.bat to get rid of the old SDK files

4. Extraction process
4.1 Extract the content of the compile SDK to: [FIFE]\build\win32\
4.2 Check if there is an [FIFE]\build\win32\applications folder; if it’s in place, you know that you extracted the SDK into the correct location. One possible issue is that you’ve checked out the whole engine SVN repository instead of just trunk. In this case extract the compile SDK to: [FIFE]\trunk\build\win32 (if you want to compile trunk, otherwhise it needs to be extracted into the build\win32 directory of the branch that you want to compile)

5.1 Run [FIFE]\trunk\build\win32\update_project_files.bat.
5.2 Build files for each supported IDE can be found in the sub-directories of [FIFE]\build\win32\build_environments (code_blocks, scons, visual_studio_8, visual_studio_9).

6. The final dynamic library (_fife.pyd) is automatically moved to: [FIFE]\engine

7. Depending on the IDE you have utilized for building FIFE you either need to run [FIFE]\build\win32\update_dlls_mingw.bat (in case you built FIFE with code::blocks or scons), [FIFE]\build\win32\update_dlls_msvc2005.bat (Visual Studio 2005) or [FIFE]\build\win32\update_dlls_msvc2008.bat (Visual Studio 2008).

8. You can now start your custom FIFE build by launching the python scripts that reside in the subdirectories of [FIFE]\clients