A new user not familiar with auto* just starts with
make -f Makefile.configure
./configure
without thinking about what to do to get the configure file.
This is not useful, if the library is part of another project though.
So maybe some hints in the README file are the better way...
Regards,
Martin Bernreuther
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hallo,
how about adding the files
NEWS
README
AUTHORS
ChangeLog
Even if these are empty (you might use "touch" to create them)
this will stop "automake" complaining!
It might also be considerable to add a file "Makefile.configure"
with a content like:
all: configure Makefile.in
# Now you may proceed with ./configure and make
Makefile.in: Makefile.am configure.in aclocal.m4
automake --add-missing
configure: aclocal.m4
autoconf
aclocal.m4:
aclocal
clean:
rm -f aclocal.m4
rm -f configure
rm -rf autom4te.cache
rm -f Makefile.in
rm -f depcomp install-sh missing
A new user not familiar with auto* just starts with
make -f Makefile.configure
./configure
without thinking about what to do to get the configure file.
This is not useful, if the library is part of another project though.
So maybe some hints in the README file are the better way...
Regards,
Martin Bernreuther
Very useful, thanks
I added this in 1.3.0