• Nick Mathewson's avatar
    Start work on fancy compiler tricks to expose extra stuff to our tests · f7d654b8
    Nick Mathewson authored
    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.