This is the mail archive of the
mailing list for the Cygwin project.
Re: How does setup.exe figure out what to install by default?
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Jonathan Kamens" <jik at curl dot com>,<cygwin-apps at cygwin dot com>
- Date: Mon, 19 Nov 2001 09:34:19 +1100
- Subject: Re: How does setup.exe figure out what to install by default?
- References: <email@example.com>
----- Original Message -----
From: "Jonathan Kamens" <firstname.lastname@example.org>
Sent: Monday, November 19, 2001 8:40 AM
Subject: How does setup.exe figure out what to install by default?
> I'm trying to figure out how setup.exe decides which packages should
> be installed by default. My best guess was that "Base" categories are
> installed by default, but I couldn't find any evidence of that in the
> source code in winsup/cinstall (I looked at every instance of the word
> "base", and unless I missed it, none of them were the one that would
> key this functionality). I found code which seems to suggest that
> "Required" or "Misc" packages are installed by default, but I don't
> see anything designated "Required" or "Misc" in setup.ini, so I don't
> know how those bits would get set on a package (and I suspect that's a
> red herring because I'm not understanding it properly anyway).
> Somebody wanna give me a hint? :-)
You are looking at old source code?
$ grep -n "Base" *
choose.cc:590: && !(getpackagecategorybyname (pkg, "Base")
> Is there some Windows magic that I'm missing here?
we use the argv, argc generated by msvcrt for us.