mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-04-30 11:50:28 +02:00
0b6d8fdc28
* README: Add more info about building against an uninstalled Guile. * meta/: New directory. The proximate cause of its creation is that I want to be able to build external packages against uninstalled Guile, and to do that I need guile-tools in the PATH, but I don't want $top_builddir/libtool in the path. But it seems like a good reorganization, for things that are /about/ Guile: pkg-config files, m4 files, guile-config... then we also include uninstalled info: the environment, the pre-inst-guile script, etc. * meta/guile-1.8-uninstalled.pc.in: New pkg-config template. pkg-config prefers -uninstalled pkg-config files, if they are in its path. * meta/Makefile.am: * meta/ChangeLog-2008: * meta/gdb-uninstalled-guile.in: * meta/guile-1.8.pc.in: * meta/guile-config.in: * meta/guile.m4: * meta/guile-tools.in: Moved to meta/. * meta/guile.in: This is the new name of pre-inst-guile.in. * meta/uninstalled-env.in: And this, pre-inst-guile-env.in. * Makefile.am: * am/guilec: * am/pre-inst-guile: * check-guile.in: * configure.in: * doc/ref/Makefile.am: * gc-benchmarks/run-benchmark.scm: * test-suite/standalone/Makefile.am: * test-suite/standalone/README: * testsuite/Makefile.am: Adapt to meta/ change.
29 lines
994 B
Text
29 lines
994 B
Text
-*-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 uninstalled-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
|
|
!#
|
|
|