Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <4366C2A9.6070609@cygwin.com> Date: Mon, 31 Oct 2005 20:19:37 -0500 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050929 Thunderbird/1.0.7 Fedora/1.0.7-1.1.fc4 Mnenhy/0.7.2.0 MIME-Version: 1.0 To: Siegfried Heintze CC: cygwin AT cygwin DOT com Subject: Re: Wanted: Help translating classpath from CMD.EXE to bash References: <15567636 DOT 1130803860651 DOT JavaMail DOT SYSTEM AT CCC-NOVA1> In-Reply-To: <15567636.1130803860651.JavaMail.SYSTEM@CCC-NOVA1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 10/31/2005, Siegfried Heintze wrote: > >As someone mentioned, you can use "cygpath -p" to convert a POSIX-style > >> path into a Win32-style one. > > > I think I need to go the other way. Given a CLASSPATH variable in windows, > how do I convert it to cygwin? Do I use ":" to separate the elements, or do > I use "\;". If I use ":", what about the windows device names? > > It seems to me this should have worked, but it does not: > * CLASSPATH=.\;c:\\dev\\xalan\\xalan-j_2_7_0\\xsltcservlet.jar\;others > * export $CLASSPATH > * echo ${CLASSPATH} > * javac myprogram.java If you're running from bash or any other Cygwin shell, then the path is already in POSIX form. 'javac' won't understand this, since it is a Windows program. 'cygpath' is the way to convert between POSIX paths and Windows/DOS, forward and back. In your case, you want POSIX->Windows/DOS conversion. See 'man cygpath' for more details. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/