Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 13 Jan 2003 14:39:00 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: javac on cygwin Message-ID: <20030113193900.GD1242@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030104115231.62364.qmail@web10401.mail.yahoo.com> <5.2.0.9.2.20030104080555.01e83058@pop3.cris.com> <5.2.0.9.2.20030104161638.01fbee88@pop3.cris.com> <20030105013147.GC11814@redhat.com> <3E2312E4.2000006@cotagesoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E2312E4.2000006@cotagesoft.com> User-Agent: Mutt/1.5.1i 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? Yes. cgf -- 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/