-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ola,

some of you might have noticed that in the last few days, i have worked
a bit on the Gem autotools based build system.

this most likely means, that Gem won't compile anymore if you just do an
"svn update" and do as you are used to.

the good thing is, that the autotools build system is now (almost)
complete, with handcruft slowly fading out.

what you have to take into account (aka major changes):

- - the root of the build system is no longer .../Gem/src but .../Gem/

in order to build Gem from a fresh checkout you now do
~$ cd .../Gem
.../Gem$ ./autogen.sh
.../Gem$ ./configure
.../Gem$ make
.../Gem$ make install

which should (by default) install everything into
/usr/local/lib/pd/extra (Gem + plugins + help-patches+manuals will be
installed into pd/extra/Gem/ and extras will be installed as (e.g.)
/usr/local/lib/pd/extra/pix_drum/

- - there are some compat scripts (.../Gem/src/autogen.sh and
.../Gem/src/configure) to ease transition (esp. for the autobuild system)

these scripts basically only call their equivalents in .../Gem and pass
all arguments.

these dummy scripts will most likely generate an error when doing an
"svn update" in an already configured tree as it will want to overwrite
the (old auto-generated) ...Gem/src/configure; simply delete the
generated configure script and rerun "svn update" to get the new stub.

i hope that having the build-system properly working (again) helps for
the next release.

fgamr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4MKhcACgkQkX2Xpv6ydvShEQCfdUhH9b9ISvxJ8euQVnFB+VA7
EB4AniEkLQuRcHW9NdRoUT2dfLJNox2Y
=ZUH3
-----END PGP SIGNATURE-----