X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
Date: Tue, 10 Feb 2009 16:26:25 -0600 (CST)
From: Tim McDaniel <tmcd@panix.com>
To: cygwin@cygwin.com
Subject: Re: RFE?: CygWinDir in ENV? (was Re: How does one find where Cygwin    was  installed from Windows?)
In-Reply-To: <4991EB3C.3090800@cygwin.com>
Message-ID: <Pine.NEB.4.64.0902101617520.3221@panix2.panix.com>
References: <4990B031.4050807@tlinx.org> <4990B128.7030004@cygwin.com>   <4990CB8D.3050704@tlinx.org> <4990D05A.4050202@cygwin.com> <4990DA52.9050900@tlinx.org>   <4990E0BF.1010502@cygwin.com> <4990EC89.8070901@tlinx.org>  <4991004F.1080006@cygwin.com>  <4991E1CC.9060804@tlinx.org>  <Pine.NEB.4.64.0902101450530.21431@panix1.panix.com> <4991EB3C.3090800@cygwin.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Tue, 10 Feb 2009, Larry Hall (Cygwin) wrote:
> Tim McDaniel wrote:
>> I have several "trampoline" scripts, a bat file
>> doing nothing but invoking a corresponding bash shell script or Perl
>> program.  I have to hard-code a location for the bash / perl
>> interpreter, but those locations change from user to user (some people
>> install under c:\, some under the standard location).  I would like to
>> have the scripts work for any system.
>
> This can be done now,

That appears to contradict what you wrote yesterday:

] If you need to do this generically for any batch file, then yes, you
] have to rely on external data and heuristics.  Going to the registry
] to see if it will help or searching the file system are two
] alternatives but there is no one key or one spot that will
] unequivocally give you the installation path.  Looking at the mount
] paths in the registry will work for 1.5 but is flawed for 1.7.
] Looking in the file-system may work depending on what you look for
] and where you start looking.

You did mention

] HKLM/Software/Cygwin/setup, the "rootdir" value.

But you noted that that is in version 1.7.

(When mentioning it, by the way, you might also mention REG.exe, a
program to do registry access, and the options for FOR that allow
running a program and getting the results in a variable in CMD.exe.
I hadn't heard of REG until I went searching just now.)

-- 
Tim McDaniel, tmcd@panix.com

--
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/

