libssh2/buildconf

#!/bin/sh

echo "***" >&2
echo "*** Do not use buildconf. Instead, just use: autoreconf -fi" >&2
echo "*** Doing it for you now, but buildconf may disapear in the future." >&2
echo "***" >&2

${AUTORECONF:-autoreconf} -fi "${@}"
Starting now, we use automake and libtool for the build. 2006-11-20 08:58:29 +00:00			`#!/bin/sh`

buildsystem: drop custom buildconf script, rely on autoreconf (#224) Notes: The buildconf script is currently required, because we need to copy a header around, because it is used both from the library and the examples sources. However, having a custom 'buildconf'-like script is not needed if we can ensure that the header exists by the time it is needed. For that, we can just append the src/ directory to the headers search path for the examples. And then it means we no longer need to generate the same header twice, so we remove the second one from configure.ac. Now, we can just call "autoreconf -fi" to generate the autotools files, instead of relying on the canned sequence in "buildconf", since autoreconf has now long known what to do at the correct moment (future versions of autotools, automake, autopoint, autoheader etc... may require an other ordering, or other intermediate steps, etc...). Eventually, get rid of buildconf now it is no longer needed. In fact, we really keep it for legacy, but have it just call autoreconf (and print a nice user-friendly warning). Don't include it in the release tarballs, though. Update doc, gitignore, and travis-CI jobs accordingly. Credit: Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Sam Voss <sam.voss@rockwellcollins.com> 2020-07-01 20:44:08 +02:00			`echo "***" >&2`
			`echo "*** Do not use buildconf. Instead, just use: autoreconf -fi" >&2`
			`echo "*** Doing it for you now, but buildconf may disapear in the future." >&2`
			`echo "***" >&2`
From: Steven Van Ingelgem <steven@vaningelgem.be> check first for libtoolize, and then for glibtoolize Mac OS X (and others?) needs this 2009-07-17 23:38:41 +02:00
buildsystem: drop custom buildconf script, rely on autoreconf (#224) Notes: The buildconf script is currently required, because we need to copy a header around, because it is used both from the library and the examples sources. However, having a custom 'buildconf'-like script is not needed if we can ensure that the header exists by the time it is needed. For that, we can just append the src/ directory to the headers search path for the examples. And then it means we no longer need to generate the same header twice, so we remove the second one from configure.ac. Now, we can just call "autoreconf -fi" to generate the autotools files, instead of relying on the canned sequence in "buildconf", since autoreconf has now long known what to do at the correct moment (future versions of autotools, automake, autopoint, autoheader etc... may require an other ordering, or other intermediate steps, etc...). Eventually, get rid of buildconf now it is no longer needed. In fact, we really keep it for legacy, but have it just call autoreconf (and print a nice user-friendly warning). Don't include it in the release tarballs, though. Update doc, gitignore, and travis-CI jobs accordingly. Credit: Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Sam Voss <sam.voss@rockwellcollins.com> 2020-07-01 20:44:08 +02:00			`${AUTORECONF:-autoreconf} -fi "${@}"`