Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Wed, 12 Jun 2002 19:06:43 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: System-wide mutexes and pthreads Message-ID: <20020612230643.GA23479@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <005401c2124e$7cb91a90$0200a8c0 AT lifelesswks> <028001c21252$e92c7ba0$6132bc3e AT BABEL> <3D07C4E0 DOT 2050603 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D07C4E0.2050603@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Wed, Jun 12, 2002 at 06:02:08PM -0400, Charles Wilson wrote: >This reminded me of something.... > >Robert -- once upon a time the idea was bandied about to create a >"subcygwin" static library that used only native, non-cygwin calls to >directly access the cygwin mount table and sort of duplicate the >functionality of (only) these two functions from cygwin.dll: > > cygwin_conv_to_full_win32_path > cygwin_conv_to_posix_path > >[I'm sure this code is already in setup.exe's codebase -- somewhere]. The code is in setup.exe's codebase and in cygcheck's codebase. I think I tried to write cygcheck's code with this in mind but it's been a while. I didn't try to deal with symlinks or recursive mounts, though. That's tricky. That's why path_conv::check is so large. I have no problem with anyone adapting the code in cygcheck for use in some program, as long as the program is GPLed. cgf