Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 4 Sep 2000 14:02:28 -0400
To: cygwin AT sources DOT redhat DOT com
Subject: Re: DLL naming conventions
Message-ID: <20000904140228.A24873@cygnus.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <17B78BDF120BD411B70100500422FC6309E0C3 AT IIS000> <001b01c0166d$d8f49d90$f7c723cb AT lifelesswks> <39B3B044 DOT 765E2666 AT ece DOT gatech DOT edu> <39B3BB23 DOT 852CAEBF AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <39B3BB23.852CAEBF@ece.gatech.edu>; from cwilson@ece.gatech.edu on Mon, Sep 04, 2000 at 11:09:23AM -0400

On Mon, Sep 04, 2000 at 11:09:23AM -0400, Charles S. Wilson wrote:
>Maybe the problem isn't solved by AppPath, after all.

From my reading of DejaNews and MSDN, I don't think that AppPath is a
solution at all.

It only seems to be invoked when you run something by double clicking on
it.  There were complaints that programs invoked from the command prompt
did not recognize it.

There is also the burden of installing this in the registry.  I don't
think that is solvable.  Not every cygwin package is going to have an
installer.

Of course, if we ever write our "registry as a file system" module for
cygwin, you could have a tar file which extracted executables to /bin
and registry information to /registry/LocalMachine/Software/...

I've spent a couple of hours rereading my various Windows Internals
books.  I had this (futile?) dream that binutils could somehow be
modified to allow cygwin to "do the right thing" as far as shared
libraries were concerned.

I don't see how that is possible though without essentially inventing
our own shared libraries.

The delayed loading stuff that is in VC 6 was sort of interesting.  I
actually use a technique very similar to VC's delayed loading in cygwin.
I thought briefly that this might be a solution but delayed loading
doesn't work with data elements, so that makes it unusable for generic
shared library support.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com