Installation depends on automake

[atg]

On OS X:

$ ./autogen.sh
./autogen.sh: line 2: autoreconf: command not found

$ brew install autoreconf
Error: No available formula with the name "autoreconf"

~ googles ~

$ brew install automake

$ ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4 
autoreconf: configure.ac: tracing
autoreconf: running: glibtoolize --copy --force
Can't exec "glibtoolize": No such file or directory at /usr/local/Cellar/autoconf/2.69/share/autoconf/Autom4te/FileUtils.pm line 345, <GEN2> line 5.
autoreconf: failed to run glibtoolize: No such file or directory
autoreconf: glibtoolize is needed because this package uses Libtool

Do you think you could throw in a configure script or something?

[julian-klode]

JFTR: configure files and their friends are not supposed to be shipped in repositories, only in tarballs, as they are generated code.

Is a release tarball available anywhere? Installing blake2 outside GNU/Linux (like Busybox/Linux or BSD) gets more painful if the GNU autotools are a compile-time dependency.

[QuLogic]

The tarball added on the releases page last week should not require automake.

[willbryant]

This is sort of still an issue because there are useful commits from 8 months ago that still haven't been tagged and released, so we end up having to build from git.

Perhaps it would be worth pursuing PR #2 to support building using CMake instead?

[emmenlau]

The tarball added on the releases page last week should not require automake.

The current tarball (libb2-0.98.1.tar.gz) requires automake, autoconf and libtool to build. Would it be possible to re-consider adding cmake (together with autotools or in place of them)?

[QuLogic]

You need to download the tarball, not the Source code that GitHub automatically creates. The configure script is included there, so I don't know what you mean about requiring autotools.