Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: [APPS] ping python maintainer (and others) - Launching cygwin apps from cmd.exe vs. softlinks in /bin
Date: Mon, 20 Sep 2004 17:48:13 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.GSO.4.61.0409201200280.29980@slinky.cs.nyu.edu>
Message-ID: <NUTMEGERq8GdHDIGX61000000bd@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 20 Sep 2004 16:48:13.0859 (UTC) FILETIME=[9EBC9730:01C49F31]

> -----Original Message-----
> From: Igor Pechtchanski  
> Sent: 20 September 2004 17:07


> >   Using a non-symbolic link works for me; "ln /bin/python2.3.exe
> > /bin/cmd-invokable-python.exe" gets me something I can 
> invoke from either
> > DOS/cmd or bash/sh.
> 
> Alternatively, you could Google for "vi.bat site:cygwin.com" 
> and apply the same technique to python.

  Fair enough, but what I really want is something that doesn't require my
makefiles to have to discriminate between what kind of python exe is first
in the path; I want them to be equipotent, and I don't want to have to
install things that aren't standard; I want a makefile that can be invoked
from either cmd.exe or bash, that can run on a system that has either cygwin
python or win32 python or both installed, that isn't sensitive to which one
comes in which order in $PATH, and that doesn't require anything extra to be
installed.  But I guess I could always use a makefile rule to create
python.bat in the objdir I'm building in.... hmm.  That might have been a
bit simpler than my current solution, which uses a fairly gross makefile
hack to search $PATH and some default install locations for any instances of
python.exe, then discards any which live in a ".../bin/.." subdir to try and
eliminate the cygwin version!

> c) the code in spawn.cc currently treats any file with a .exe 
> extension
> specially, and passes it on to CreateProcess without looking 
> into it any
> more than that.  It could, technically, check whether the file is an
> old-style symlink, and do the right thing in that case -- as always,
> <http://cygwin.com/acronyms/#PTC>.


  LOL, I don't really think it's within my abilities to come up with a patch
for spawn.cc that modifies the behaviour of cmd.exe....... 

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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