mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-05-01 04:10:18 +02:00
3394818c0a
* test-suite/standalone/Makefile.am (test_cflags): Add `-I$(top_builddir)' so that <config.h> can be found. (snarfcppopts): Likewise. * test-suite/standalone/*.c: Include <config.h>. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile.am | ||
| README | ||
| test-asmobs | ||
| test-asmobs-lib.c | ||
| test-bad-identifiers | ||
| test-conversion.c | ||
| test-gh.c | ||
| test-list.c | ||
| test-num2integral.c | ||
| test-require-extension | ||
| test-round.c | ||
| test-system-cmds | ||
| test-unwind.c | ||
| test-use-srfi | ||
| test-with-guile-module.c | ||
-*-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 that 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 !#