[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Size of TSVN msi installer, need your opinion

From: Tim Schultze <tschultze_at_nuthatchsoftware.com>
Date: Sun, 13 Sep 2015 10:37:30 -0400

I'm going to guess that the amount of activity on this list would be
significantly higher if you rely on the second installation step for
that percentage of machines that don't have the run-time on them. It
would seem traffic on this list is skewed (understandably) to
installation issues as the dominant minority subject. I've never seen a
complaint about the size of the installer, and as someone else pointed
out, installers in the range of 40MB are pretty common. I would agree
with the suggestion that you statically link until there is a better
technological solution. Keep your focus on continuing to enhance and
solidify this amazing gift to the development community.

On 9/12/2015 5:03 AM, Stefan Küng wrote:
> Hi,
> Because the c-runtime merge modules provided by Microsoft with VS2015
> are completely broken (you've noticed that if you installed 1.9.0 x64 -
> you had to also install the runtime separately), I've changed the TSVN
> build for 1.9.1 to statically link with the c-runtime.
> That actually lead to a small size reduction of the installer msi.
> But linking the c-runtime statically lead now to other problems:
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3136728
> That's because the c-runtime keeps global state memory for every dll
> separately. This unfortunately includes output to stdout, for which
> there is no workaround.
> So now I could change the TSVN build to link *everything* statically,
> getting rid of the apr/svn dlls. But that means that every exe now
> increases in size. Especially all the command line exe (svn, svnadmin,
> svnserve, svnversion, ...).
> This would fix all the problems that arise if the c-runtime is linked
> statically to multiple dlls - because we wouldn't use separate dlls anymore.
> But of course, that doubles the size of the msi installer.
> 1.9.0 32-bit : 15.8MB
> 1.9.0 64-bit : 20.3MB
> fully static link:
> 32-bit : 30.8MB
> 64-bit : 39.2MB
> So the 64-bit msi is almost 40MB in size now.
> So, what should I do?
> Link everything statically and have the msi use almost 40MB for a download?
> Or go back to linking dynamically to the c-runtime, but not include the
> merge modules (as I said: they're broken). That would require that all
> users install the c-runtime distributable manually. If the runtime is
> not installed, then TSVN would throw errors and would not start.
> Opinions?
> Stefan


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-09-13 16:37:48 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.