|
From: strk <st...@ke...> - 2007-09-22 07:10:03
|
On Fri, Sep 21, 2007 at 11:16:17PM +0200, peterdd wrote: > When running configure > ./configure --disable-python --disable-php --disable-tcl You shouldn't need them, all are disabled by default, you need --enable-xxx to selectively enable those you need. > It tries to do some work in the extension directories too. > Why? ./configure must create the Makefile there, from Makefile.in The alternative would be giving each binding it's own build scripts which would likely mean making it much harder to test the bindings before installing Ming. > IMHO it isn't needed and I should even be able to delete the unneeded > extension dirs? If you comment out the lines referring to those subdirs in the configure.in (AC_OUTPUT) and in the top-level Makefile.am (SUBDIRS) you can then delete the unneeded extension dirs. > Reason: Want prepare the release for only one language extension with c-source > included on a repository for that programming language. (perl CPAN.org) > Probably get rid of autotools finally for that and clean up, but want just > start with a working starting point. I'm pretty much in favor of packaging the core lib separately from the bindings. The need to keep all the bindings in sync is also a problem which slows down development of the core library. --strk; |