[GEM-dev] bug in makefile

IOhannes m zmoelnig zmoelnig at iem.at
Wed Oct 18 14:53:32 CEST 2006


Mathieu Bouchard wrote:
> On Wed, 18 Oct 2006, IOhannes m zmoelnig wrote:
> 
> Because everyone expects a source tarball in which ./configure already 
> exists and that things are in a way cleaner if the tarball is *exactly* 
> the same as a cvs export.

hmm...
i expect a INSTALL.txt, where i can read how to build. if it says 
"aclocal && autoconf && ./configure && make" i can understand this and 
follow. (however, it adds more dependencies to build)

in theory Gem's build system just needs "make" (and does the rest on its 
own).
since flags to configure are needed, i am thinking about using some 
environment variable for configure-flags:

~> make CONFIGURE_FLAGS="--with-pd=/bi/ba/bo"

would then run:
  aclocal
  autoconf
  ./configure --with-pd=/bi/ba/bo
  make

i don't understand why things are cleaner if tarballs and CVS export are 
the same. (it might give you less worried users, but that has nothing to 
do with cleanliness)

mf.asdr
IOhannes




More information about the GEM-dev mailing list