Hi Mikhael!
You probably misunderstood me. I said at the beginning that I am using
Autoconf+Automake now, and did not like it and then you recommended me to
using them, and also gave me an AC/AM 101 on how to do it. (which wasn't
necessary, because I already discovered it myself using trial and error and
reading the docs).
The problem with Autoconf and Automake is that it takes too damn long to
prepare the program for testing. I need to:
1. Create a dist. (make distdir)
2. cd there and invoke configure with a prefix set to a local directory
3. "Compile" and install everything which is a recursive make.
Another factor is that some of my tests are written in bash and are very
comprehensive and so are kind of slow. But that can be fixed. Still, the
preparation time for the testing is noticable.
One option to fix it would be to generate my own custom Makefile.in which
would later be processed by ./configure to create Makefile. (and so ditch
automake). This solution works quite well for the Subversion people where
Greg Stein wrote a build system generator in Python. (I can do it with perl).
And I had positive experiences with the speed scalability of a centralized
makefile architecture. (there's also Peter Miller's "Recursive Make
Considered Harmful" article which I haven't read yet[1] ).
Still, it would be quite a lot of work on my part, and I'll have to think how
I can resolve all the issues I put forth with it effectively. I'm hoping to
avoid that.
Regards,
Shlomi Fish
[1] - http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html
On Tuesday 13 April 2004 01:41, Mikhael Goikhman wrote:
> On 12 Apr 2004 05:55:22 +0300, Shlomi Fish wrote:
> > I have developed Quad-Pres, which is a presentation tool based on Perl
> > and Web Meta Language (http://thewml.org/) first for my own use and now
> > distribute as open source software.
> >
> > Now, up to now, after I revamped the program to be centralized in the
> > system, I used GNU Autoconf and Automake to manage the program's
> > "compilation" and installation. The problem is that now I have several
> > tests and the process I'm using to invoke them from Autoconf is "icky":
> > it's slow, cumbersome and unfit for a Perl program.
> >
> > I'm looking for a nice alternative installer, preferablly written in Perl
> > (which I can already assume is installed there), that I can use to
> > perform the preparation, testing and installation. Rolling something on
> > my own should not be too hard, but I'd rather use an available solution
> > if possible.
>
> [requirements skipped]
>
[Autoconf/Automake 101 snipped]
---------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Homepage: http://shlomif.il.eu.org/
Quidquid latine dictum sit, altum viditur.
[Whatever is said in Latin sounds profound.]
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
