Hi! I think many of you are aware of the bindingsplit branch, which rearranges the swig files so that it is possible to build bindings for different languages in several modules instead of just one big one.
This is beneficial for the following reasons: - Solves problems in os's that cant link so many symbols in one module. - Needs less memory to build the whole thing. (addressing #258, #210) The python bindings are already adapted to build as several modules, and they can serve as reference implementation for people from other languages. As is now, it should be possible to just build other languages in the old way, or using the cooleer new split approach :). Note languages that where working before must provide a backwards compatible way of using the modules, which means some glue code. The main thing which is needed now for merging the branch to trunk is testing all languages in that branch, both those already adapted for new ways (python) and the ones still building monolitically (java, perl). It is specially important to check that java and perl still work as before with no changes to the branch. If any errors are encountered, please report. I have added further information at: http://www.crystalspace3d.org/main/BindingsSplit, for other language bindings maintainers specially, and in general for those interested. Greetings and thx!! 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]
