2 Mar
2004
2 Mar
'04
9:32 a.m.
On Tue, 2004-03-02 at 05:46, Matthias Nagorni wrote:
On Tue, 2 Mar 2004, Dave Robillard wrote:
Fair enough. ./configure etc. is without a doubt THE way to distribute
free software though. Most people find it quite annoying when an app
doesn't follow the 'standard'.
Users simply don't like hand-editing and copying configuration files
around. At the very simplest level I don't want to edit the Makefile to
make AMS use my preferred CFLAGS, and know where to find QT, and install
to /usr. I just want to "./configure --prefix=/usr" and be done with it.
-Dave
On Mon, 2004-03-01 at 23:53, Mark Johnathan
Greenaway wrote:
> On Mon, Mar 01, 2004 at 11:36:42PM -0500, Dave Robillard wrote:
> > > I'm quite a fan of alsamodularsynth and have been recommending it to
> > > friends. The only problem I have with it is that rather than use
> > > automake/autoconf for building it has Makefiles that only work without
> > > editing under SuSE. Of course, editing the Makefiles to get it to build
> > > on other distributions and installing the required development packages
> > > is trivial.
You only have to edit the library path constants at the beginning of
the Makefile. If you have adapted that to the requirements of your system
once, you can just copy and paste it in any new Makefile of any new ams
release. It's indeed trivial. I don't like the idea of automake/autoconf.
I've got the impression that these pose more problems than they are
actually solving. So unless somebody convinces me, I won't include this
mechanism into the official ams tarball.