Duncan Mac-Vicar Prett wrote:
On Wednesday 25 July 2007 11:41:42 Stefan Hundhammer wrote:
Having separate directories makes building and packaging a lot easier IMHO. You also don't need to install all kinds of other language development packages if you don't need a certain language. Also, different development tools (autotools vs. cmake) make it hard to keep everything in one directory, in particular since cmake builds out-of-source-tree and the autotools inside the source tree.
Yes, but also makes sharing code between the bindings impossible.
For example, if you want to generate bindings for the libraries, the swig stuff will be the same for ruby and python.
Still, I am ok with its own directory. (or we could use cool-bindings/ for ruby and python :-P )
Or you can use two different directories: * One for ruby-bindings * Another for YaST-bindings containing the common libraries shared by another bindings as well. We use the in YaST already: * yast2.rpm contains several shared libraries * Other YaST modules share some code using the yast2.rpm (Network/Firewall/IP/Popup...) It doesn't make sense to have some duplicate code but it makes sense to have smaller RPM-based directories (such as perl-bindings, ruby-bindings, python-bindings...) Just my opinion :) Bye Lukas