Mercurial > fife-parpg

view build/win32/README.txt @ 697:ecaa4d98f05f tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Abstracted the GUI code and refactored the GUIChan-specific code into its own module. * Most of the GUIChan code has been refactored into its own gui/guichan module. However, references to the GuiFont class still persist in the Engine and GuiManager code and these will need further refactoring. * GuiManager is now an abstract base class which specific implementations (e.g. GUIChan) should subclass. * The GUIChan GUI code is now a concrete implementation of GuiManager, most of which is in the new GuiChanGuiManager class. * The GUI code in the Console class has been refactored out of the Console and into the GUIChan module as its own GuiChanConsoleWidget class. The rest of the Console class related to executing commands was left largely unchanged. * Existing client code may need to downcast the GuiManager pointer received from FIFE::Engine::getGuiManager() to GuiChanGuiManager, since not all functionality is represented in the GuiManager abstract base class. Python client code can use the new GuiChanGuiManager.castTo static method for this purpose.
author M. George Hansen <technopolitica@gmail.com>
date Sat, 18 Jun 2011 00:28:40 -1000
parents 295b7ba75020
children
line wrap: on
line source

==========================
FIFE Win32 compile guide for building the 2009.0 release version
==========================

Installation / build process
==========================
1. Check out the latest engine sources from SVN:
Repository URL: http://fife.svn.cvsdude.com/engine/trunk

2.1 Get the latest compile SDK for Win32 from the FIFE wiki:
http://wiki.fifengine.de/index.php?title=Download_section#Compile_SDKs
2.2 Get ActivePython 2.5 and install it to a location of your choice:
http://downloads.activestate.com/ActivePython/windows/2.5/ActivePython-2.5.1.1-win32-x86.msi

3. Extraction process
3.1 Extract the content of the compile SDK to:
<FIFE>\build\win32\
3.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)


4.1 Run <FIFE>\trunk\build\win32\update_project_files.bat.
4.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).

5. The final dynamic library (_fife.pyd) is automatically moved to:
<FIFE>\engine

6. 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).

7. You can now start your custom FIFE build by launching the python scripts that reside in the subdirectories of <FIFE>\clients.