On Tue, 10 Jun 2008 12:49:34 +0100, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Fri, 6 Jun 2008 17:20:35 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Fri, 6 Jun 2008 15:31:38 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
...
To sum it up: I'm not against any autotools based solution, I just won't work it myself.
Fair enough, but I think it's probably the best choice.
It seems no one else agrees with me about the common configure script ;-)
I was thinking, probably anything is better than nothing, so perhaps committing the configure script you wrote that just calls the subdirectory configures would be useful. If you want to write a waf
I'm not sure, it is really not very good and definetely needs a lot of love. Anyway, I committed the files but it is not even working because the Makefile.am's of the plugin directories contain SUBDIRS = po ... but there are no Makefile.* in the various plugin directories as their creation is currently disabled in the configure.in. To not attempt users to use this, I moved the files into the directory 'buildtest'. For actual testing, they should be moved in the toplevel directory above.
subdirectory configures would be useful. If you want to write a waf system this would be useful too. I assume most linux devs have python anyway.
Yes, I will do this, at some point. Not in the next days :D.
Regards, Enrico