ctdb-build: Separate test backtrace support into separate subsystem
authorMartin Schwenke <martin@meltin.net>
Tue, 3 May 2022 23:02:12 +0000 (09:02 +1000)
committerAmitay Isaacs <amitay@gmail.com>
Thu, 28 Jul 2022 08:35:50 +0000 (18:35 +1000)
commit7f3fb453d63e944366730db6f227f46d1327e036
tree3d38f91b28b0bb1bdc82c1e29ef18700e879e201
parent71637715857ccc031aa5588ee6d5b256e5283c41
ctdb-build: Separate test backtrace support into separate subsystem

A convention when testing members of ctdb-util is to include the .c
file so that static functions can potentially be tested.  This means
that such tests can't be linked against ctdb-util or duplicate symbols
will be encountered.

ctdb-tests-common depends on ctdb-client, which depends in turn on
ctdb-util, so this can't be used to pull in backtrace support.
Instead, make ctdb-tests-backtrace its own subsystem.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
ctdb/wscript