This is the mail archive of the
mailing list for the Cygwin project.
Re: Optimized Cygwin package
- From: David Stacey <drstacey at tiscali dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Mon, 04 Nov 2013 17:45:28 +0000
- Subject: Re: Optimized Cygwin package
- Authentication-results: sourceware.org; auth=none
- References: <1383561297008-104027 dot post at n5 dot nabble dot com> <1873370490 dot 20131104164740 at mtu-net dot ru> <5277AE3A dot 2010104 at cs dot utoronto dot ca>
On 04/11/13 14:24, Ryan Johnson wrote:
On 04/11/2013 7:47 AM, Andrey Repin wrote:
Today my Cygwin package is around 1.4Gb.
I've tried to restrict amount of package required by distribution,
lot of dependencies are required.
Does someone know how to restrict and optimize Cygwin packages
using it only for this applications?
Given your list - no.
Actually, I'm surprised you've managed to wrest it into 1.5Gb.
Something sounds very wrong about that...
Off the top of my head, I would expect GCC to be ~100MB, python
30-60MB, shocked if perl/TCL were each larger than 100MB, mintty is
measured in kB, most shells and Make are a handful of MB. Doxygen has
no strange dependencies.
- shell (mainly tcsh)
Even assuming maximal package sizes, that's only 400MB. Where exactly
would you expect the other 1GB come from?
Running 64-bit setup.exe pulls the following default package set
FYI: The 32-bit version of doxygen is a little more interesting, as it
has clang assisted parsing enabled. Hence 32-bit doxygen also pulls in
libclang, along with whatever dependencies libclang requires.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple