| commit | 7a1c43fc745c09e8dd95eae3de4cebc0678e4110 | |
| author | Martin Schwenke <martin@meltin.net> | |
| Tue, 3 May 2022 23:02:12 +0000 (4 09:02 +1000) | ||
| committer | Martin Schwenke <martins@samba.org> | |
| Thu, 28 Jul 2022 10:09:34 +0000 (28 10:09 +0000) | ||
| tree | c63d085d58e6922fa53956825748bcb14b823063 | treesnapshot (tar.gz zip) |
| parent | b195e8c0d0c597be87387f477ebfb62244979e39 | commitdiff |
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>
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 | diffblobblamehistory |