diff options
author | fanquake <fanquake@gmail.com> | 2021-10-04 13:03:38 +0800 |
---|---|---|
committer | fanquake <fanquake@gmail.com> | 2021-10-05 11:38:28 +0800 |
commit | 747cd17404832604c50d03d58e11ba816bb229f7 (patch) | |
tree | fe04e2ee6f095d17485b83da4d44ce66cefdd4ad /src/secp256k1 | |
parent | 446b706696451ae1a66ac416f347d734c5741d7c (diff) |
build: no-longer fail default configure if BDB isn't available
Inline with moving to descriptor (sqlite) wallets by default for 0.23,
this adapts the build system so that a default `./configure` invocation
no-longer fails if BDB isn't present. Currently, if configure is run
with no options, and no BDB is present, we'll fail with:
```bash
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for BDB wallet support (--without-bdb to disable BDB wallet support)
```
If descriptor wallets are to be the default, this behaviour no longer
makes sense, as a builder should be able to configure and build, to use
a wallet, without BDB installed, and without passing additional
arguments, i.e `--without-bdb` or `--with-incompatible-bdb`, to
configure.
With this change, running configure will no-longer fail, and will
instead print:
```bash
checking for Berkeley DB C++ headers... no
configure: WARNING: libdb_cxx headers missing
configure: WARNING: Bitcoin Core requires this library for BDB (legacy) wallet support
configure: WARNING: Passing --without-bdb will suppress this warning
checking for sqlite3 >= 3.7.17... yes
checking whether to build wallet with support for sqlite... yes
```
Diffstat (limited to 'src/secp256k1')
0 files changed, 0 insertions, 0 deletions