See readme: You need the automake utilites. But anyway, I
will acc the ./configure to next releases.
3.1 Linux
To compile avra you need gcc and the automake utilities.
These will create
a ./configure script that evaluates your system
enviroment. To get the
avra executable, you have to issue the following commands:
aclocal
autoconf
automake -a
./configure
make && make install
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, the more usual way to do do this is to add the generated configure script (only) in the tarball for distribution. So there's less work for the normal user (i.e. they don't need compatible automake tools, etc., which is often a problem). Developers downloading form CVS can be assumed to have the right tools.
The automake-compile script does help, but Linux and Mac OS X users need to run it sudo (for the install to work) and it does not support passing options (like --prefix) to the configure script. Neither does it give help if the user does not have the right tools installed. Supplying the configure script would be much better. The automake-compile script is a useful hint to developers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
See readme: You need the automake utilites. But anyway, I
will acc the ./configure to next releases.
3.1 Linux
To compile avra you need gcc and the automake utilities.
These will create
a ./configure script that evaluates your system
enviroment. To get the
avra executable, you have to issue the following commands:
aclocal
autoconf
automake -a
./configure
make && make install
Logged In: NO
Have a look at the README file (not sure if it's already in there in 1.1.1, but it is in the newer versions):
aclocal
autoconf
automake -a
./configure
make && make install
which means you have to generate the configure script yourself using autoconf.
Logged In: YES
user_id=1270801
Originator: NO
Yes, the more usual way to do do this is to add the generated configure script (only) in the tarball for distribution. So there's less work for the normal user (i.e. they don't need compatible automake tools, etc., which is often a problem). Developers downloading form CVS can be assumed to have the right tools.
The automake-compile script does help, but Linux and Mac OS X users need to run it sudo (for the install to work) and it does not support passing options (like --prefix) to the configure script. Neither does it give help if the user does not have the right tools installed. Supplying the configure script would be much better. The automake-compile script is a useful hint to developers.