mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-09-22 14:04:58 +02:00
f7d654b81e
This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests. |
||
|---|---|---|
| .. | ||
| bench.c | ||
| include.am | ||
| Makefile.nmake | ||
| ntor_ref.py | ||
| test_addr.c | ||
| test_cell_formats.c | ||
| test_config.c | ||
| test_containers.c | ||
| test_crypto.c | ||
| test_data.c | ||
| test_dir.c | ||
| test_introduce.c | ||
| test_microdesc.c | ||
| test_ntor_cl.c | ||
| test_pt.c | ||
| test_replay.c | ||
| test_util.c | ||
| test-child.c | ||
| test-network.sh | ||
| test.c | ||
| test.h | ||