diff options
author | Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> | 2021-11-28 18:13:52 +0200 |
---|---|---|
committer | Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> | 2021-11-28 18:13:52 +0200 |
commit | 83c08ba0c97798e7da2d4e74722ece534d0f8620 (patch) | |
tree | 6c620aa8182f1d294002630f4b10c869ac8a07a9 /depends | |
parent | 4f8b1f8759301d2553183e14f72444a0f1d80725 (diff) | |
download | bitcoin-83c08ba0c97798e7da2d4e74722ece534d0f8620.tar.xz |
doc: Fix typos in packages.md
Diffstat (limited to 'depends')
-rw-r--r-- | depends/packages.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/depends/packages.md b/depends/packages.md index 7ed20ea129..4158b46d28 100644 --- a/depends/packages.md +++ b/depends/packages.md @@ -178,8 +178,8 @@ not sufficient to just say `libprimary`. For us, it's much easier to just link a static `libsecondary` into a shared `libprimary`. Especially because in our case, we are linking against a dummy `libprimary` anyway that we'll throw away. We don't care if the end-user has a -static or dynamic `libseconday`, that's not our concern. With a static -`libseconday`, when we need to link `libprimary` into our executable, there's no +static or dynamic `libsecondary`, that's not our concern. With a static +`libsecondary`, when we need to link `libprimary` into our executable, there's no dependency chain to worry about as `libprimary` has all the symbols. ## Build targets: |