You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use pkg-config where we can, which generally replaces libtool at a
higher level and does not have the same downsides as libtool. These
archives sit in our depends tree with no purpose and pollute the final
bitcoin build with massive overlinking.
Copy file name to clipboardExpand all lines: depends/packages.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,18 @@ Most autotools projects can be properly staged using:
151
151
152
152
$(MAKE) DESTDIR=$($(package)_staging_dir) install
153
153
154
+
## Build outputs:
155
+
156
+
In general, the output of a depends package should not contain any libtool
157
+
archives. Instead, the package should output `.pc` (`pkg-config`) files where
158
+
possible.
159
+
160
+
From the [Gentoo Wiki entry](https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Handling_Libtool_Archives):
161
+
162
+
> Libtool pulls in all direct and indirect dependencies into the .la files it
163
+
> creates. This leads to massive overlinking, which is toxic to the Gentoo
164
+
> ecosystem, as it leads to a massive number of unnecessary rebuilds.
165
+
154
166
## Secondary dependencies:
155
167
156
168
Secondary dependency packages relative to the bitcoin binaries/libraries (i.e.
0 commit comments