Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: Add script to fetch and build BDB 4.8 in-tree? #3971

Closed
laanwj opened this issue Mar 28, 2014 · 2 comments
Closed

build: Add script to fetch and build BDB 4.8 in-tree? #3971

laanwj opened this issue Mar 28, 2014 · 2 comments

Comments

@laanwj
Copy link
Member

laanwj commented Mar 28, 2014

Lots of people get stumped by the BDB 4.8 dependency. It is starting to be really hard to get in modern distros. Even if we were to go to some magic append-only wallet format we'll have to support it for foreseeable time for backwards compatibility.

I think a script that fetches BDB 4.8, configures and builds it statically would be useful.
Then change the bitcoin autoconf to automatically pick it up (and set include/library path accordingly) if it was fetched this way.

Note: I am not proposing to add BDB to the git repository like we did with leveldb. Just to make building against the "holy version" easier.

@laanwj laanwj changed the title build: Add way to fetch and build BDB 4.8 in-tree? build: Add script to fetch and build BDB 4.8 in-tree? Mar 28, 2014
@laanwj laanwj added the Wallet label Mar 28, 2014
@Belkaar
Copy link

Belkaar commented Mar 28, 2014

Why not include the source and directly build it into the binary?
db 4.8 needs to stay in for the foreseeable future anyways to import old wallets.

@laanwj
Copy link
Member Author

laanwj commented Mar 29, 2014

There is already too much 'alien' code in here (leveldb, spirit-json), I want to reduce the amount of code in 'core' not increase it.

BDB is only used for the wallet and the wallet is planned to be split off to a seperate repository (see #3882). After that, at some point, including the BDB code may be acceptable. But I also doubt it (also depends on license issues and such).

This is an intermediate solution, which would be acceptable to even the most conservative devs and could be easy to implement and it is effectively the same as including it if done right.

@laanwj laanwj closed this as completed Apr 7, 2014
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants