Following https://github.com/libarchive/libarchive/wiki/BuildInstructions#building-libarchive-from-the-github-source-code, when v3.6.2 is built from distribution tarball (https://www.libarchive.org/downloads/libarchive-3.6.2.tar.gz) and by checking out the git tag (https://github.com/libarchive/libarchive/releases/tag/v3.6.2), the generated files seems different. These are the results I got (target directory names should be self-explanatory)
root@c468ac8cddcc:~# tree /tmp/libarchive-with-autotools-from-tarball/lib/
/tmp/libarchive-with-autotools-from-tarball/lib/
|-- libarchive.a
|-- libarchive.la
|-- libarchive.so -> libarchive.so.13.6.2
|-- libarchive.so.13 -> libarchive.so.13.6.2
|-- libarchive.so.13.6.2
`-- pkgconfig
`-- libarchive.pc
1 directory, 6 files
root@c468ac8cddcc:~# tree /tmp/libarchive-with-cmake-from-git-tag/lib/
/tmp/libarchive-with-cmake-from-git-tag/lib/
|-- libarchive.a
|-- libarchive.so -> libarchive.so.19
|-- libarchive.so.19
`-- pkgconfig
`-- libarchive.pc
1 directory, 4 files
By print-debugging, I confirmed that both the methods compute interface version to be 19, but for some reason the build from tarball creates .so.13.6.2 file while the one from git tag creates .so.19 file. Any idea why it is so?
Following https://github.com/libarchive/libarchive/wiki/BuildInstructions#building-libarchive-from-the-github-source-code, when v3.6.2 is built from distribution tarball (https://www.libarchive.org/downloads/libarchive-3.6.2.tar.gz) and by checking out the git tag (https://github.com/libarchive/libarchive/releases/tag/v3.6.2), the generated files seems different. These are the results I got (target directory names should be self-explanatory)
By print-debugging, I confirmed that both the methods compute interface version to be
19, but for some reason the build from tarball creates.so.13.6.2file while the one from git tag creates.so.19file. Any idea why it is so?