| Hi: you all know that there are 2 sets of perl/python/php bindings: *) one based on swig in module/swig/{perl5,php,python} that accesses the 1wire bus directly *) one based on the owserver protocol in module/ownet/{perl5,php,python} The problem with the current configure script is that disabling swig or one of the swig bindings (./configure --enable-swig=no or ./configure --enable-owperl=no --enable-php=no --enable-python=no) also prevents the installation of the corresponding ownet binding. This is really a nuisance, since it is often useful to install just the bindings from ownet, without being forced to compile/install the whole swig thing. The enclosed patch tries to solve this by decoupling the --with-python --with-perl5 --with-php options from the corresponding --enable-ow{perl5,php,python} options. So, considering for example python, if this patch is applied: --with-python=no disables both module/ownet/python and module/swig/python --enable-swig=no disables the whole module/swig --enable-ownet=no disables the whole module/ownet --enable-owpython=no disables only module/swig/python This latter options is somehow redundant with my patch: in fact --with-python --enable-swig and --enable-ownet are clearly orthogonal to each other, while --enable-owpython lies in the space spanned by --with-python and --enable-swig. However I was unsure if it would be acceptable to drop this well known option. Stefano |
0001-enable-perl5-php-python-in-module-ownet-even-if-modu.patch
Description: Binary data
------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
