Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From:	"Chris January" <chris AT atomice DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: javac on cygwin
Date:	Wed, 15 Jan 2003 09:07:42 -0000
Message-ID:	<LPEHIHGCJOAIPFLADJAHAEFODDAA.chris@atomice.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
In-Reply-To:	<20030113193900.GD1242@redhat.com>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

> On Mon, Jan 13, 2003 at 11:26:28AM -0800, Shankar Unni wrote:
> >Christopher Faylor wrote:
> >>I remember speculating at one point about creating wrappers to the
> >>win32 functions like CreateFile, MoveFile, etc.  which would understand
> >>cygwin paths.  You could theoretically modify an .exe to load
> >>cygwin1.dll and use the wrapper functions.  Or you could use some of
> >>Windows hook facilities to do that.
> >
> >Hmm.  Would that even work?

This is a project I might work on when I have the time.

Chris


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -