(as discussed in #3377)
-logtodebugger is a strange, obscure, WIN32-only (mostly MSVC) thing. It went untested for a long time, so I'm pretty sure that noone is using it. Let's clean up the options a bit get rid of it.
test_bitcoin was using fLogToDebugger as a way to prevent logging to debug.log. For this, add a boolean (not exposed as option) fLogToDebugLog that defaults to true and is disabled in the tests.
`-logtodebugger` is a strange, obscure, WIN32-only (mostly MSVC) thing.
Let's clean up the options a bit get rid of it.
test_bitcoin was using fLogToDebugger as a way to prevent logging to
debug.log. For this, add a boolean (not exposed as option) fLogToDebugLog that
defaults to true and is disabled in the tests.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/9e9056cd1a05e5868025553d2a8cb3e47cf45045 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
Untested ACK.
I've also never used this (and don't use MSVC), so ACK on removing it.