X-Spam-Check-By: sourceware.org
Message-ID: <43E2CAE4.D1FEB4AE@dessent.net>
Date: Thu, 02 Feb 2006 19:15:48 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: mismatched dll
References: <020220062158 DOT 387 DOT 43E28079000ACE870000018322007507440A050E040D0C079D0A AT comcast DOT net> <20060203013712 DOT GC17485 AT brasko DOT net> <43E2B779 DOT 4371E33B AT dessent DOT net> <20060203030045 DOT GE17485 AT brasko DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Bob Rossi wrote:

> Nice, I was wondering how you could develop on Cygwin without this
> capability. That makes perfect sense. I'm just guessing, but it might be
> a good idea to make this hardcoded constants dynamic, so that any
> arbitrary number of cygwin1.dll's can coexist.

I can imagine that it should be possible for someone relatively familiar
with the cygwin build system to write in a few hours a patch that would
parameterize this, so that you could do something like

./configure --with-shared-id=foobar \
            --with-mount-table-id=foobar --with-dllname=foobar

and end up with a "cygfoobar1.dll" that uses "foobar" in the shared
memory region name and registry mount keys.  Then (using the proper gcc
parameters) you could compile your package to use this cygfoobar1.dll
and have no dependence on cygwin1.dll, and be completely isolated from
any existing cygwin on a system.

Of course, nobody associated with Cygwin would then want anything to do
with trying to support such a frankensteined installation.  And it's not
clear to me that such a patch would even be accepted.  But it should be
relatively easy.

Brian

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