The following 2 steps worked for me
1) Use semicolon as path separator
2) Enclose the whole path string inside double quote
Example
javac -classpath ".;poi-3.2-FINAL-20081019.jar" SR.java
--
View this message in context:
http://www.nabble.com/path-separator-tp17704083p22813149.html
> From: samitj
> Subject: Re: path separator
>
>
> hmm... i thought cygwin emulates a unix shell in windows.
> $ echo $PATH
> /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/WINDOW
> S/system32:/cygdri.
>
> anyway, if i use a windows separator (;), it d
if u r trying to say something different, do u have a solution to
make that work ?
Mark J. Reed-2 wrote:
>
> On Fri, Jun 6, 2008 at 9:17 PM, samitj <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>> what is the path separator in Cygwin for paths, classpaths etc..
>>
>&
samitj wrote:
what is the path separator in Cygwin for paths, classpaths etc..
this works...
$ java -cp lib/matrix/matrix.jar
com.test.matrix.simulation.SimulationApplication
this fails..
$ java -cp lib/matrix/matrix.jar:bin/
com.test.matrix.simulation.SimulationApplication
Exception in
On Fri, Jun 6, 2008 at 9:17 PM, samitj <[EMAIL PROTECTED]> wrote:
>
> Hi,
> what is the path separator in Cygwin for paths, classpaths etc..
>
> this works...
> $ java -cp lib/matrix/matrix.jar
> com.test.matrix.simulation.SimulationApplication
Java is not a Cygwin pa
Hi,
what is the path separator in Cygwin for paths, classpaths etc..
this works...
$ java -cp lib/matrix/matrix.jar
com.test.matrix.simulation.SimulationApplication
this fails..
$ java -cp lib/matrix/matrix.jar:bin/
com.test.matrix.simulation.SimulationApplication
Exception in thread "
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Greg Fenton
> --- Max Bowsher <[EMAIL PROTECTED]> wrote:
> >
> > No: Cygwin != _WIN32.
> >
>
> No argument from me here. :-)
>
>
> > A native/Cygwin dual-mode binary sounds like a clever idea, but AFAIK
> > has never been done before
separate directory names
and the file name when forming a path.
General rules for applications creating names for directories and files or
processing names supplied by the user include the following:
Use any character in the current code page for a name, but do not use a path
separator, a
--- Larry Hall <[EMAIL PROTECTED]> wrote:
>
> Max is right (surprised Max? ;-) ) But I want to point out something
> else about what you've said. If your main concern is paths, don't
> convert '/' to '\'. Windows understands both under the hood.
> (Cygwin
> does too but that's another matter).
Max Bowsher wrote:
Greg Fenton wrote:
--- Max Bowsher <[EMAIL PROTECTED]> wrote:
No: Cygwin != _WIN32.
No argument from me here. :-)
A native/Cygwin dual-mode binary sounds like a clever idea, but AFAIK
has never been done before, and is probably ridiculously infeasible on
the balance of wor
Greg Fenton wrote:
> --- Max Bowsher <[EMAIL PROTECTED]> wrote:
>>
>> No: Cygwin != _WIN32.
>>
>
> No argument from me here. :-)
>
>
>> A native/Cygwin dual-mode binary sounds like a clever idea, but AFAIK
>> has never been done before, and is probably ridiculously infeasible on
>> the balance of
--- Max Bowsher <[EMAIL PROTECTED]> wrote:
>
> No: Cygwin != _WIN32.
>
No argument from me here. :-)
> A native/Cygwin dual-mode binary sounds like a clever idea, but AFAIK
> has never been done before, and is probably ridiculously infeasible
on
> the balance of work/benefit.
I don't see th
Greg Fenton wrote:
> --- Christopher Faylor <[EMAIL PROTECTED]> wrote:
>>
>> You shouldn't be defining _WIN32 for cygwin. Cygwin gcc doesn't
>> define this by default.
>
>
> Unfortunately, autoconf is doing this for us. It is picking up
> windows.h from /usr/include/w32api, which in turn includes
--- Christopher Faylor <[EMAIL PROTECTED]> wrote:
>
> You shouldn't be defining _WIN32 for cygwin. Cygwin gcc doesn't
> define this by default.
Unfortunately, autoconf is doing this for us. It is picking up
windows.h from /usr/include/w32api, which in turn includes windef.h.
Besides, we *do*
On Tue, Jun 03, 2003 at 10:09:11AM -0700, Greg Fenton wrote:
>I am looking to enhance SWISH-E ( http://www.swish-e.org )to support
>Cygwin. It builds and runs just fine, but internally the code takes a
>configuration parameter and if it is a shell-command, converts all of
>the "/" characters to "\
at runtime whether we're in Cygwin (how?)
- use an environment variable to determine the appropriate path
separator (is there one?)
Thanks in advance,
greg_fenton.
=
Greg Fenton
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! Calendar - Free online ca
16 matches
Mail list logo