Repository navigation
|
Hi, I noticed a significant difference in the size of the x86_64-qbittorrent-nox binary between the recent qBittorrent 5.2.3 releases. For comparison: qBittorrent 5.2.3 + libtorrent 2.0.13 — binary size is around 34 MB I'm specifically comparing the x86_64-qbittorrent-nox files from these releases. What I find interesting is that the 5.2.3 + libtorrent 2.0.13 build has a normal size, while both the 2.0.14 and 1.2.20 builds are almost twice as large. Since the 1.2.20 build is also significantly larger, I'm wondering whether this is related to the libtorrent source itself or to the build/linking configuration. In particular, could someone clarify whether there were any changes in the build process affecting: CFLAGS / CXXFLAGS / LDFLAGS It would be particularly helpful to know whether the increase is expected for these libtorrent versions, or whether it might indicate that some optimization/stripping step is no longer being applied. The fact that both libtorrent 1.2.20 and 2.0.14 produce ~64 MB binaries, while 2.0.13 produces ~34 MB, makes me suspect there may be a build-system or linker-related difference rather than simply an increase in libtorrent code size. If anyone has compared the relevant workflow/build scripts between these releases, I'd appreciate some insight into what changed. Thanks! |
Replies: 1 comment
|
They are built with Icu enabled which increases file size. This is the default for releases moving forward. |
They are built with Icu enabled which increases file size. This is the default for releases moving forward.