Hi!

I just merged bindingsplit branch into trunk. This means now the swig
files are ready for building bindings in several modules instead of just
one big module, which should help memory and linking problems for most
users. Keep in mind atm only python is using the new approach to
building the bindings, so thats where the changes can be noticed, java
and perl should still work as before.

For python users working with trunk, there are three things to keep in mind:

1- You should take care to delete any old cspace.py/.pyc/.pyo,
_cspace.dll, _cspace.so and related files from your last build, as they
wont be taken care of by the adapted build system, and having the old
ones laying around will most certainly lead to problems.

2- Python bindings won't be built in main cs directory any more, but in
out/<platform>/<debug/optimize>/bindings/python/. This means python will
not find the modules automatically, so you have to take care to set the
PYTHONPATH yourselves (there doesn't seem to be a good solution to avoid
this).

3- libcrystalspace_python does not exist any more (might affect people
doing bindings for their own projects based on crystalspace ones). Also
static builds now have to distribute the full bindings folder including
so/dlls, building these in is not supported any more.

Other than this, all should be 100% compatible with previous way of
doing things.

Also note CEL python will be broken for couple hours until i commit the
necessary changes to make it work again (mainly account for
libcrystalspace_python dissapearing). The python modules in csextra and
csexternal will be adapted also if needed.

Finally, the branch has been tested by some people and myself, but still
some errors might have escaped unnoticed, so please report any problems
either here, in irc or trac.

 Pablo


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Crystal-main mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: mailto:[EMAIL PROTECTED]

Reply via email to