diff options
| author | fanquake <fanquake@gmail.com> | 2023-11-29 12:08:37 +0000 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-12-01 10:46:19 +0000 |
| commit | 308aec3e5655327d98e0428d8205d246f24d6af5 (patch) | |
| tree | c65b252202a63771443d38c86fc1557fe235f274 /build_msvc/bitcoin_config.h.in | |
| parent | 35537318a19360ddf1ea8f0c1e6d8ad49e635516 (diff) | |
| download | bitcoin-308aec3e5655327d98e0428d8205d246f24d6af5.tar.xz | |
build: disable external-signer for Windows
It's come to light that Boost ASIO (a Boost Process sub dep) has in some
instances, been queitly initialising our network stack on Windows (see
PR #28486 and discussion in #28940).
This has been shielding a bug in our own code, but the larger issue
is that Boost Process/ASIO is running code before main, and doing things
like setting up networking. This undermines our own assumptions about
how our binary works, happens before we get to run any sanity checks,
and also runs before we call our own code to setup networking.
It's also not clear why a feature like external signer would have a
dependency that would be doing anything network/socket related, given it
only exists to spawn a local process.
Diffstat (limited to 'build_msvc/bitcoin_config.h.in')
| -rw-r--r-- | build_msvc/bitcoin_config.h.in | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/build_msvc/bitcoin_config.h.in b/build_msvc/bitcoin_config.h.in index 1716647486..ec69307f50 100644 --- a/build_msvc/bitcoin_config.h.in +++ b/build_msvc/bitcoin_config.h.in @@ -41,9 +41,6 @@ /* Define this symbol to enable ZMQ functions */ #define ENABLE_ZMQ 1 -/* define if external signer support is enabled (requires Boost::Process) */ -#define ENABLE_EXTERNAL_SIGNER /**/ - /* Define to 1 if you have the declaration of `be16toh', and to 0 if you don't. */ #define HAVE_DECL_BE16TOH 0 |