X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
Message-ID: <4F3440BE.1090402@cwilson.fastmail.fm>
Date: Thu, 09 Feb 2012 16:55:10 -0500
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
Reply-To: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Tcl/tk  dll's
References: <4F32FC8A DOT 4040602 AT gmail DOT com> <1328753679 DOT 2032 DOT 12 DOT camel AT YAAKOV04>
In-Reply-To: <1328753679.2032.12.camel@YAAKOV04>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

On 2/8/2012 9:14 PM, Yaakov (Cygwin/X) wrote:
> On Wed, 2012-02-08 at 23:51 +0100, marco atzeri wrote:
>> curiosity, any reason why the tcl/tk  dll's are
>> not using the cyg prefix ?
> 
> In fact, there is.  The point of the "cyg" prefix is to avoid possible
> mismatches with MinGW DLLs using the "lib" prefix.  In this case,
> however, forcing a "cyg" prefix with Tcl's unique build system would be
> a lot of work for no gain, since Tcl already has its own way of
> distinguishing between the two (tclXY.dll vs. libtclX.Y.dll).  Note that
> python and R (in Ports) do the same thing for the same reason.

Sadly, for the (in progress) cygwin-fork-that-shall-not-be-named version
of tcl/tk, I have to do this, because to be a good citizen I have to
avoid conflicting with cygwin's DLLs (libfooX.Y.dll) and 'native' DLLs
(fooXY.dll).  Thus, I've already developed all the necessary patches to
make this work -- and the changes, incl. those to the in-tcl build
system for TEA extensions, are not that difficult.

However, if cygwin's tcl/tk packages were to *now* adopt such a patch,
then it would cause no end of back-compatibility issues and Yet Another
Recompile Of All Clients.  And that's a Heaping Plateful of Pain, for no
real benefit.

So, for once, I actually agree with Yaakov on one of these issues --
which is why I never mentioned the existence of my patch prior to the
Big Tcl/Tk Transition.

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple