I have tried quite a few things, let me summurise:
- I have walked into the python debugger through tutorial1.py, and some plugins are loaded Ok, some are not because there symbol in python is lost.
I have reduced the python test case to what seems a minimal length:
from cspace import *
object_reg = csInitializer.CreateEnvironment(sys.argv)
def Report (severity, msg):
csReport(object_reg, severity, "crystalspace.application.python", msg)
if not csInitializer.SetupConfigManager(object_reg):
Report(CS_REPORTER_SEVERITY_ERROR, "Couldn't init app!")
plugin_requests = [CS_REQUEST_IMAGELOADER]
if not csInitializer.RequestPlugins(object_reg, plugin_requests):
Report(CS_REPORTER_SEVERITY_ERROR, "Plugin requests failed!")
The 'iImageIO' symbol is still valid until the code enter csInitializer.RequestPlugins(object_reg, plugin_requests), where for some reasons it get losts.
From there, since I am not expecting a symbol to disappear magically, I suspect that some code in python or generated swig has done some evil things.
I have tried:
python 2.6.4 + swig 1.3.36 => ko
python 2.5.4 + swig 1.3.36 => ko
python 2.5.4 + swig 1.3.31 => ko
so, when falling to python 2.5 and swig 1.3.31, I thinck I am back to 'rather stable' (I have done a quick search on the swig tracker but did not find anything striking).
So, before going into very new thing for me which would be to step into python code to understand what is happening, can someone state the version of python, swig, gcc that is working for you on release crystal 1.4 ? Please tell me if you are compiling 'optimized' code or debug.