From: Bart Veer <bartv@ecoscentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: #! magic for finding Cygwin Tcl shell
Date: Tue, 06 Jan 2009 20:01:00 -0000 [thread overview]
Message-ID: <pnvdss2ogx.fsf@delenn.bartv.net> (raw)
In-Reply-To: <49639C9C.9040607@dallaway.org.uk> (message from John Dallaway on Tue, 06 Jan 2009 18:02:04 +0000)
>>>>> "John" == John Dallaway <john@dallaway.org.uk> writes:
John> I was looking at support for UNC file paths in the eCos
John> Configuration Tool today. The convoluted #! magic we use in
John> our Tcl scripts to find a Cygwin Tcl shell is getting in the
John> way when calling (eg) heapgen.tcl via a UNC repository path.
John> This code is only needed to support installations of Cygwin
John> that are more than 5 years old.
John> Rather than increase the complexity of the #! magic still
John> further, I think it now makes sense to revert to a simple
John> "#! /usr/bin/tclsh" within our Tcl scripts. However, this
John> would break compatibility with old Cygwin installations
John> providing only tclsh8*.exe or cygtclsh80.exe.
John> Any objections?
There is another approach we could consider. Instead of invoking
"tclsh", we could invoke "ecosconfig tclsh". That would require a
minor change to ecosconfig. Combine that with a statically linked
build of ecosconfig, and we should end up with something much more
robust than the current approach of depending on whatever version of
Tcl happens to be installed, somewhere, under some name or other.
However, any changes along those lines should probably wait until
after the 3.0 release. AFAIK, what we have right now seems to work
well enough.
Bart
--
Bart Veer eCos Configuration Architect
eCosCentric Limited The eCos experts http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
next prev parent reply other threads:[~2009-01-06 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 18:02 John Dallaway
2009-01-06 18:51 ` Jonathan Larmour
2009-01-06 19:10 ` Gary Thomas
2009-01-06 19:44 ` Jonathan Larmour
2009-01-07 9:44 ` John Dallaway
2009-01-07 13:39 ` Jonathan Larmour
2009-01-07 17:06 ` John Dallaway
2009-01-06 19:13 ` John Dallaway
2009-01-06 19:37 ` Jonathan Larmour
2009-01-06 20:04 ` Sergei Gavrikov
2009-01-06 20:01 ` Bart Veer [this message]
2009-01-07 11:10 ` Tarmo Kuuse
2009-01-07 11:53 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pnvdss2ogx.fsf@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).