Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <4.2.2.20000612173539.00b3d690@gqserver.houston.geoquest.slb.com> X-Sender: wjin AT gqserver DOT houston DOT geoquest DOT slb DOT com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 12 Jun 2000 17:47:21 -0700 To: cygwin AT sourceware DOT cygnus DOT com From: Woody Jin Subject: Re: Make and javac compliler problem in bash In-Reply-To: <4.1.20000612174900.02307940@pop.mathworks.com> References: <4 DOT 2 DOT 2 DOT 20000612160752 DOT 00a78a50 AT gqserver DOT houston DOT geoquest DOT sl b.com> <4 DOT 1 DOT 20000612144728 DOT 01f06100 AT pop DOT mathworks DOT com> <4 DOT 2 DOT 2 DOT 20000612131311 DOT 00b313c0 AT gqserver DOT houston DOT geoquest DOT sl b.com> <4 DOT 1 DOT 20000612114500 DOT 02abfa80 AT pop DOT mathworks DOT com> <4 DOT 2 DOT 2 DOT 20000612100114 DOT 00b2faa0 AT gqserver DOT houston DOT geoquest DOT sl b.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 06:21 PM 6/12/00 -0400, Paul Kinnucan wrote: > >>Did you actually try running make in Unix mode as suggested in the FAQ? > > > > > >Of course. > > > >And what happened? Were you able to get your makefile to work? If it had worked, I wouldn't even have bothered to ask here :-) >I said "without any additional information" because you couched your >requirement in a general way. The solution you're suggesting requires that >a user install Cygwin and create a mount table that maps DOS to Unix paths. > >I suspect this is a solution of limited appeal to most developers of >Windows applications, including Sun. > >It would be great if Sun or someone else ports javac to Cygwin, but at the >moment javac is a native Windows application and that was the situation I >addressed in my original response to you. Yes, the above is one of the solution that I suggested. Ask them to recognize the Cygwin community. But a better way would be to resolve it within Cygwin. By default, any application that is not in cygwin may be considered as Windows native application (WNA). So, when you launch WNAs, cygwin can convert the unix style directory to DOS style. After the conversion, pass the converted MS-DOS style path to the WNA. I don't know why you think that this is so impossible or so difficult. It is just putting the gvim's functionality into Cygwin. If an application that is not WNA and not in Cygwin, cygwin may provide some facility to register those applications. Maybe any application that uses cygwin.dll may be considered as non-WNAs. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com