HCoop / bpt / guile.git / blame
| Commit | Line | Data |
|---|---|---|
| eda9f0e6 RB |
1 | -*-text-*- |
| 2 | ||
| 3 | These tests use the standard automake TESTS mechanism. Tests should | |
| 4 | be listed in TESTS in Makefile.am, and should exit with 0 on success, | |
| 5 | non-zero on failure, and 77 if the result should be ignored. See the | |
| 6 | automake info pages for more information. | |
| 7 | ||
| 8 | If you want to use a scheme script, prefix it as follows: | |
| 9 | ||
| 10 | #!/bin/sh | |
| 11 | exec guile -s "$0" "$@" | |
| 12 | !# | |
| 13 | ||
| 14 | Makefile.am will arrange for all tests (scripts or executables) to be | |
| 0b6d8fdc | 15 | run under uninstalled-env so that the PATH, LD_LIBRARY_PATH, and |
| eda9f0e6 RB |
16 | GUILE_LOAD_PATH will be augmented appropriately. |
| 17 | ||
| 18 | The Makefile.am has an example of creating a shared library to be used | |
| 19 | from a test scheme script as well. | |
| 20 | ||
| 21 | You can also create standalone executables that include your own code, | |
| 22 | are linked against libguile, and that run a given test script (or | |
| 23 | scripts). One way to do this is to create the binary, make sure it | |
| 24 | calls scm_shell (argc, argv) as its final action, and put this bit at | |
| 25 | the top of your test script: | |
| 26 | ||
| 27 | #!./my-test-binary -s | |
| 28 | !# | |
| 29 |