1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-05-11 00:00:49 +02:00
guile/test-suite/standalone
Rob Browning 479c46eab8 * standalone/test-asmobs-lib.c (libtest_asmobs_init): include
test-asmobs-lib.x rather than test-asmobs-lib.x.c.
2003-04-14 15:55:23 +00:00
..
.cvsignore * standalone/.cvsignore: new file. 2003-04-07 17:37:53 +00:00
Makefile.am * standalone/Makefile.am: change from .c.x to .x to be consistent 2003-04-14 15:55:18 +00:00
README * standalone/README: new file. 2003-04-07 17:46:11 +00:00
test-asmobs * standalone/test-asmobs: new test script. 2003-04-07 17:46:30 +00:00
test-asmobs-lib.c * standalone/test-asmobs-lib.c (libtest_asmobs_init): include 2003-04-14 15:55:23 +00:00
test-gh.c * standalone/test-gh.c: new test code (migrated from 2003-04-07 17:48:00 +00:00
test-num2integral.c * standalone/test-num2integral.c: new test -- one new regression 2003-04-07 17:48:31 +00:00

-*-text-*-

These tests use the standard automake TESTS mechanism.  Tests should
be listed in TESTS in Makefile.am, and should exit with 0 on success,
non-zero on failure, and 77 if the result should be ignored.  See the
automake info pages for more information.

If you want to use a scheme script, prefix it as follows:

  #!/bin/sh
  exec guile -s "$0" "$@"
  !#

Makefile.am will arrange for all tests (scripts or executables) to be
run under pre-inst-guile-env so tht the PATH, LD_LIBRARY_PATH, and
GUILE_LOAD_PATH will be augmented appropriately.

The Makefile.am has an example of creating a shared library to be used
from a test scheme script as well.

You can also create standalone executables that include your own code,
are linked against libguile, and that run a given test script (or
scripts).  One way to do this is to create the binary, make sure it
calls scm_shell (argc, argv) as its final action, and put this bit at
the top of your test script:

  #!./my-test-binary -s
  !#