moonunit-lt [--plugin module] [--wrap command_prefix] moonunit_parameter | libtool_library ...
moonunit-lt allows libtool library (.la) files to be used with moonunit. Libraries will be relinked as necessary and a modified set of parameters will be passed to moonunit.
This script allows MoonUnit tests to be compiled and run as part of a project built with libtool. All types of libraries -- including static -- are supported. Non-libtool libraries will still work as expected.
As a convenience to plugin writers, moonunit-lt also supports loading additional libtool libraries as plugins.
moonunit-lt expects a list of parameters as appropriate for moonunit, with the exception that libtool library files may safely be specified.
In addition, the following options are available:
--plugin module
Allows module (which should be a libtool library) to be
found and loaded as a MoonUnit plugin. This is useful
for testing a new plugin within its own build tree.
--wrap command_prefix
Prefixes the invocation of moonunit with
command_prefix, e.g. gdb --args.
This is used primarily for testing moonunit itself.
-h, --helpLists brief usage and option information in addition to that provided by moonunit.
moonunit-lt mylib.laRun all unit tests in the libtool library mylib.la.
moonunit-lt --plugin mylogger.la -l mylogger mylib.la
Run all unit tests in the libtool library mylib.la, logging
results using the logger plugin in the libtool library mylogger.la.
moonunit-lt --wrap valgrind mylib.la
Run all unit tests in the libtool library mylib.la, with
moonunit itself being run in the memory debugger
valgrind.