X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Message-ID: <47E909C3.3010408@hdfgroup.org>
Date: Tue, 25 Mar 2008 09:18:43 -0500
From: Scott Wegner <swegner@hdfgroup.org>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Remove Cygwin Path for Called Batch Script
References: <47E8FE86.9020405@hdfgroup.org> <47E90794.3010406@sbcglobal.net>
In-Reply-To: <47E90794.3010406@sbcglobal.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.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

Greg Chicares wrote:
> On 2008-03-25 13:30Z, Scott Wegner wrote:
>> I am trying to create a "wrapper" Cygwin bash script to add 
>> functionality to an existing Windows batch script.  In my Cygwin script, 
>> I would like to call the batch file with something like:
>>
>> ...
>> cmd.exe /k batch-script.bat params
>> ...
>>
>> Calling the script in this fashion seems to generally work (in that the 
>> script executes).  However, I have trouble because the Cygwin path is 
>> prepended to the Windows path in the batch script.  As a result, trying 
>> to use the Windows "find" use Cygwin's instead.
> 
> If you write
>   %SystemRoot%\system32\find
> in the batch file, then you'll get the msw "find" whether or not
> any Cygwin directory is on your path.

Hi Greg,

Thanks for the quick reply.  This is a feasible solution.  However, I'd 
rather find a solution where the batch script can remain "unaware" of 
its Cygwin context.  Once I get things working, I plan on creating bash 
script wrappers for many Windows batch scripts, so I'd like to make the 
changes in the Cygwin environment, rather than editing each batch script 
individually.

I'll keep looking at let you know if I find anything.

Scott

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

