@theuni When running gitian on master, I noticed we export the following files:
13fb68cdb26c104c29617864bee264bd426ec19f29c1ed9de9c30322d9cd5edd 32/include/bitcoinconsensus.h
6e3697e010639696225b84965f8c8fe17a62663a8a0afdbdb3250cf02c605c48 32/lib/libbitcoinconsensus.a
4ab6383eb015a6b7d51ca4ec589f7e9c96d605456be26e0893ba5a231b620903 32/lib/libbitcoinconsensus.so
4ab6383eb015a6b7d51ca4ec589f7e9c96d605456be26e0893ba5a231b620903 32/lib/libbitcoinconsensus.so.0
4ab6383eb015a6b7d51ca4ec589f7e9c96d605456be26e0893ba5a231b620903 32/lib/libbitcoinconsensus.so.0.0.0
- The
.soand.hmake sense - they are necessary to use the library. - However - we're exporting the library three times! I suppose we should remove the
.0and.0.0.0, even as symbolic links it doesn't make much sense to package them?
-rwxr-xr-x 1 orion orion 1193440 Nov 21 17:53 libbitcoinconsensus.so
-rwxr-xr-x 1 orion orion 1193440 Nov 21 17:53 libbitcoinconsensus.so.0
-rwxr-xr-x 1 orion orion 1193440 Nov 21 17:53 libbitcoinconsensus.so.0.0.0
- I don't think exporting the static
.alibrary is a good idea as it is not self-contained, unlike the shared library (as well as exposing a lot of internal symbols, and having unclear dependencies that need to be linked too).