X-Spam-Check-By: sourceware.org
Date: Mon, 31 Jul 2006 09:51:31 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: "Dr. Christoph Gille" <christoph DOT gille AT charite DOT de>
cc: cygwin AT cygwin DOT com
Subject: Re: cygwin
In-Reply-To: <64932.84.190.50.192.1154335251.squirrel@webmail.charite.de>
Message-ID: <Pine.GSO.4.63.0607310941500.5912@access1.cims.nyu.edu>
References: <64932 DOT 84 DOT 190 DOT 50 DOT 192 DOT 1154335251 DOT squirrel AT webmail DOT charite DOT de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mon, 31 Jul 2006, Dr. Christoph Gille wrote:

> Dear Mr Pechtcha,

Peshansky, actually...

> Searching the mailing-list for an answer to my CYGWIN problem I found
> a posting from you about a related topic and hope that you might be
> able to help me.
>
> Please appologize that I contact you directly before
> posting to the mailing list

As described in <http://cygwin.com/acronyms/#PPIOSPE>, it's almost always
better to post to the list, unless private email is specifically requested
by the other party.

> The Java program I write has some embedded C and Fortran source code
> and therefore requires standard compilers which are absent on XP and
> Windows2000.
>
> Therefore the Java program downloads cygwin setup.exe and launches
> setup.exe.
>
> Before launching setup.exe it tells the user to select the program
> gnu-make and the compilers for C, C++ and f77 in the devel group.
>
> I would prefere if it could select it automatically to enable
> unattended installation of these software components.
>
> Further I want the installation in driveLetter:\cygwin\ because the
> Java program needs to find the cygwin installation on HD.
>
> The only choice the user has to make is the driveLetter.
>
> What would be the best way to initiate a tailored installation on
> a client running my Java program.

Cygwin setup.exe supports a variety of command-line options.  Googling for
"cygwin setup command-line options" should unearth a list (or run "setup
--help" and examine the file setup.log).  You might have better luck with
newer setup snapshots (from <http://cygwin.com/setup/snapshots>).

Selecting packages might be a problem in your situation.  There's an
experimental patch for package selection via the command line -- search
the cygwin-apps list archives.  If you are willing to setup a mirror site
for your users, you can use the empty package with dependences trick that
I posted numerous times to the Cygwin mailing list (Google for "cygwin
automated install").

> Many thanks for your help
> Christoph Gille
>
> P.S.
>
> I think that this is a general problem
> which should be in in the FAQs. What is your opinion ?

There are too many variations for this to make a concise FAQ entry.
Perhaps a chapter in the User's Guide?
<http://cygwin.com/acronyms/#SHTDI> and <http://cygwin.com/acronyms/#PTC>.
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/