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 sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Apparently-From: To: cygwin AT sourceware DOT cygnus DOT com Subject: Cygwin and JVMs From: Galen Boyer Date: 29 Jan 2001 14:54:29 -0500 Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 Lines: 17 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii How does one deal with the classpath's and other environmental variables when porting scripts between windows and unix, using the cygwin tools of course. For context, we are using weblogic, ejb, java, toplink and verve. We right now have *.cmd files to compile and start the application. Is there a way to *.sh files executing in the cygwin environment that can then be ported to the UNIX machine? We keep having to deal with the classpath separators and drive-letters right now and can't get one script for both platforms. Thanks. -- Galen Boyer Fingers and toes, fingers and toes, forty things we share. Forty one if you include, the fact that we don't care. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple