This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: #! magic for finding Cygwin Tcl shell
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Jonathan Larmour <jifl at eCosCentric dot com>
- Cc: John Dallaway <john at dallaway dot org dot uk>, ecos-devel at ecos dot sourceware dot org
- Date: Tue, 06 Jan 2009 12:10:15 -0700
- Subject: Re: #! magic for finding Cygwin Tcl shell
- References: <49639C9C.9040607@dallaway.org.uk> <4963A830.6090600@eCosCentric.com>
Jonathan Larmour wrote:
> John Dallaway wrote:
>> I was looking at support for UNC file paths in the eCos Configuration
>> Tool today. The convoluted #! magic we use in our Tcl scripts to find a
>> Cygwin Tcl shell is getting in the way when calling (eg) heapgen.tcl via
>> a UNC repository path. This code is only needed to support installations
>> of Cygwin that are more than 5 years old.
>>
>> Rather than increase the complexity of the #! magic still further, I
>> think it now makes sense to revert to a simple "#! /usr/bin/tclsh"
>> within our Tcl scripts. However, this would break compatibility with old
>> Cygwin installations providing only tclsh8*.exe or cygtclsh80.exe.
>>
>> Any objections?
>
> Yes, it may not be in /usr/bin. I don't mind the cygwin-specific cygpath
> bits being dropped, but I'd still want it to be found from the PATH by some
> means.
Does CygWin have '/usr/bin/env'? This is the "modern" way
to handle this:
#! /usr/bin/env tclsh
...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------