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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Steve Subject: Cygwin Bash Script Syntax Question Date: Thu, 24 Apr 2003 11:07:04 -0400 Organization: MYOB Lines: 50 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en Hi; I am using cygwin on win2k. I have a __native__ JDK 1.3 installed. I am trying to write myself a bash script to do some compiling jobs. I am having trouble getting some path syntax issues ironed out. The native java will accept either C:\FOO\FOO or C:/FOO/FOO The native java will not accept /cygdrive/c/FOO/FOO After some experimentation it seems that bash is getting confused about the ':' symbol. It seems to be interpreting the ':' in C:/foo as a path seperator so PATH=C:/foo:C:/foa is getting interpreted as specifiying these dirs: C:/foo C foo Anyway I would like to write a script that would look like this in a .sh file: ---------------------------------------- export SOURCEDIR=C:/foo export OUTDIR=C:/foa export CLASSPATH=C:/abc:C:/def:C:/ghi javac -sourcepath $SOURCEDIR -d $OUTDIR -classpath $CLASSPATH $1 ------------------------------------------ So.....what would the path syntax be like? Do I use ':' or ';' as directory seperators? Do I use '/' or '\' ? I'm sorry if this seems lame but I am getting dizzy from tyring to make a native windows installation of java work with a cygwin .sh file Any help will be appreciated STeve -- 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/