Re: [avrdude-dev] make distcheck

[Theodore A. Roth]

On Wed, 5 Mar 2003, Theodore A. Roth wrote:

:)ACLOCAL = ${SHELL} 
/home/troth/dev/tools/avrdude-cvs/obj/avrdude-3.1.0cvs/missing --run aclocal-1.7
:)AMDEP_FALSE = #
:)AMDEP_TRUE =
:)AMTAR = ${SHELL} 
/home/troth/dev/tools/avrdude-cvs/obj/avrdude-3.1.0cvs/missing --run tar
:)AUTOCONF = ${SHELL} 
/home/troth/dev/tools/avrdude-cvs/obj/avrdude-3.1.0cvs/missing --run autoconf
:)AUTOHEADER = ${SHELL} 
/home/troth/dev/tools/avrdude-cvs/obj/avrdude-3.1.0cvs/missing --run autoheader
:)AUTOMAKE = ${SHELL} 
/home/troth/dev/tools/avrdude-cvs/obj/avrdude-3.1.0cvs/missing --run 
automake-1.7
:)
:)Notice that even though all the autotools where in my PATH, it set them to 
:)use missing. Note that this was a build using the dist tarball. I think this 
:)is good, since it won't use the real tools during a build by someone who 
:)downloads the tarball.

One last note. It looks like the automake can make the distinction between 
the source from a dist tarball (show above) and a developers cvs dir (shown 
from a build from cvs source):

ACLOCAL = aclocal-1.7
AMDEP_FALSE = #
AMDEP_TRUE =
AMTAR = ${SHELL} /home/troth/dev/tools/avrdude-cvs/missing --run tar
AUTOCONF = autoconf-2.57
AUTOHEADER = autoheader-2.57
AUTOMAKE = automake-1.7

If this holds on the freebsd system, I think we can ignore it and move on.

Ted