[Crystal-develop] Scripting bindings splitting

[Pablo M. <ca...@si...>]

Hi!

As talked some time ago in this thread:
http://thread.gmane.org/gmane.comp.graphics.crystalspace.general/10725

the scripting bindings are being split into several submodules. work is
being done in a branch in svn for those interested:
https://crystal.svn.sourceforge.net/svnroot/crystal/CS/branches/feature/bindingsplit

Work is already pretty much advanced, and i'd say the splitting is
basically done, now what is left is deciding where to generate and build
the new modules files.

As an example, the split python bindings would be composed of the
following files (possibly some more in the end):

dlls:
_csgeom.so  _core.so  _iengine.so  _imesh.so    _ivaria.so  _pycscegui.so
_csgfx.so   _cstool.so  _imap.so     _isndsys.so  _ivideo.so
py files:
csgeom.py  cstool.py   imesh.py    ivideo.py
csgfx.py   iengine.py  isndsys.py  pycscegui.py
core.py  imap.py     ivaria.py
all these should end in some folder which will have some additional glue
stuff.

Questions:
1) where to build all the files in the first place?
I think building them directly under out/arch/buildstyle/python/ would
be best, but im not sure jam target is prepared for this. Note im saying
out/arch/buildstyle/python/ instead of out/arch/plugins/cscript/cspython
because i dont think its entirely appropriate any more to build the
bindings together with the embedding module. The two should be more
separate.

Another similar option would be out/arch/buildstyle/bindings/python/

2) where to place the cspace/ folder with the whole bindings after build?
Options would be: main dir, out/arch/buildstyle/python/cspace/ or
scripts/python/cspace/.

Greetings!

 Pablo