Libtool - Test descriptions

Here is a list of the current programs in the test suite, and what they test for:

demo-conf.test
demo-exec.test
demo-inst.test
demo-make.test
demo-unst.test: These programs check to see that the `demo' subdirectory of the libtool distribution can be configured, built, installed, and uninstalled correctly. The `demo' subdirectory contains a demonstration of a trivial package that uses libtool.
hardcode.test: On all systems with shared libraries, the location of the library can be encoded in executables that are linked against it see section Linking executables. This test checks the conditions under which your system linker hardcodes the library location, and guarantees that they correspond to libtool's own notion of how your linker behaves.
link.test: This test guarantees that linking directly against a non-libtool static library works properly.
link-2.test: This test makes sure that files ending in `.lo' are never linked directly into a program file.
suffix.test: When other programming languages are used with libtool (see section Using libtool with other languages), the source files may end in suffixes other than `.c'. This test validates that libtool can handle suffixes for all the file types that it supports, and that it fails when the suffix is invalid.
test-e.test: This program checks that the test -e construct is never used in the libtool scripts. Checking for the existence of a file can only be done in a portable way by using test -f.