Neil Jerram
1f2707cc94
New test for thread-safe define
|
%!s(int64=16) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| .gitignore | %!s(int64=16) %!d(string=hai) anos | |
| Makefile.am | %!s(int64=16) %!d(string=hai) anos | |
| README | %!s(int64=20) %!d(string=hai) anos | |
| test-asmobs | %!s(int64=16) %!d(string=hai) anos | |
| test-asmobs-lib.c | %!s(int64=16) %!d(string=hai) anos | |
| test-bad-identifiers | %!s(int64=16) %!d(string=hai) anos | |
| test-conversion.c | %!s(int64=16) %!d(string=hai) anos | |
| test-define-race.c | %!s(int64=16) %!d(string=hai) anos | |
| test-fast-slot-ref.in | %!s(int64=16) %!d(string=hai) anos | |
| test-gh.c | %!s(int64=16) %!d(string=hai) anos | |
| test-list.c | %!s(int64=16) %!d(string=hai) anos | |
| test-num2integral.c | %!s(int64=16) %!d(string=hai) anos | |
| test-require-extension | %!s(int64=16) %!d(string=hai) anos | |
| test-round.c | %!s(int64=17) %!d(string=hai) anos | |
| test-scm-c-read.c | %!s(int64=16) %!d(string=hai) anos | |
| test-scm-take-locale-symbol.c | %!s(int64=16) %!d(string=hai) anos | |
| test-scm-with-guile.c | %!s(int64=16) %!d(string=hai) anos | |
| test-system-cmds | %!s(int64=16) %!d(string=hai) anos | |
| test-unwind.c | %!s(int64=17) %!d(string=hai) anos | |
| test-use-srfi.in | %!s(int64=16) %!d(string=hai) anos | |
| test-with-guile-module.c | %!s(int64=16) %!d(string=hai) anos | |
README
-*-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
!#
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
!#