Static link Libbitcoin #568

New issue

Open

opened 2023-11-05 15:54:23 +00:00 by christophersanborn · 2 comments

christophersanborn commented

2023-11-05 15:54:23 +00:00

(Migrated from gitlab.com)

The current build procedure dynamically links to Libbitcoin as well as several other libraries. The other libraries are not so problematic, as they can be installed with apt-get. But Libbitcoin is not available in any standard repositories. Thus static linking greatly simplifies the remote installation procedure.

As a user and a node administrator for a handful of main-net and testnet block producing and API witness nodes, I would like the Libbitcoin libraries to be static-linked to the witness_node and cli_wallet binaries. The reason is that this would produce a single binary that I can push to a remote machine from a cloud provider, and be able to run the software, without have to manually install an assortment of supporting libraries. The current build procedure dynamically links to Libbitcoin as well as several other libraries. The other libraries are not so problematic, as they can be installed with apt-get. But Libbitcoin is not available in any standard repositories. Thus static linking greatly simplifies the remote installation procedure.

christophersanborn commented

2023-11-05 15:54:24 +00:00

(Migrated from gitlab.com)

assigned to @bgerze

bgerze commented

2023-11-06 16:10:31 +00:00

(Migrated from gitlab.com)

mentioned in merge request !254