This is the mail archive of the
mailing list for the Cygwin project.
Re: Spawning Java from C
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 23 Feb 2012 22:29:27 -0500
- Subject: Re: Spawning Java from C
- References: <4F4678CB.firstname.lastname@example.org> <4F469FDF.email@example.com>
- Reply-to: cygwin at cygwin dot com
On 2/23/2012 3:21 PM, Eliot Moss wrote:
On 2/23/2012 12:35 PM, James Rome wrote:
I have code that launches Java from C to run a jar file, and creates a
socket to communicate between the calling program and the jar file. It
works in OS X, Linux, and MinGW on Windows, but not on Cygwin.
One can definitely spawn Java from C, but every JVM I know of
is a *Windows* application, which mean that it wants *Windows
paths*, not cygwin-style paths. You may find the cygpath
utility useful in scripts run under cygwin, to convert between
different styles of path.
Java, in particular, wants things like its classpath as a
*semicolon*-separate list of *Windows* path names. These
generally require suitable quoting if being used in scripts
or with bash, since bash interprets semicolcon as separating
bash commands, etc.
As for the particular errors, I am personally less familiar
with using cygrunsrv ...
To the OP, run the same from an elevated prompt and these
errors should disappear.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple