Re: There is no need for auto*
> > Ever tried to compile a program
> > developed on GNU/Linux on, say, AIX?
> > Or even BSD?
> Yes, I did. I have a project library,
> which supports sockets, threads etc. -
> it compiles (and works) cleanly under
> Linux, FreeBSD, cygwin and Borland C++.
> I used few ifdefs (really _few_, and
> only to distinguish Win32/*ix platform),
> but that's all. So? :)
If I want to install your package in /usr/local instead of /usr, or maybe in $HOME/local, what do I have to do to make it do so?
That's one thing I like about autoconf, and it's actually the main reason I use it for my projects. I don't need to write complex install targets in my Makefiles, and force the user to edit the Makefile to change the paths. autoconf generates all the boilerplate code for me.
By the way, this is also very helpful if you write .spec files for RPMs or debian build scripts. With rpm .specs, the usual way when generating the package is to build and install it into a temporary directory, about like './configure --prefix=/usr; make; make PREFIX=/tmp/rpm1234 install'.
Admitted, autoconf is extremely complex once you get to more complicated issues, but it does the stuff I mentioned very nicely.