At 10:35 AM 11/24/99 +0200, John Leuner <[EMAIL PROTECTED]> wrote:
>Are these programs just normal java programs, or do they use a UNIX 'make'
>type language?
These are exclusively for making Java programs. I put them on auto-pilot.
Nothing to configure. Nothing to script.
>I would far prefer a version of 'make' written in Java, since it allows
>you to do all the stuff mentioned below (although it doesn't know about
>packages) and much much more.
I've heard about a JMake that runs UNIX 'make' scripts.
>I don't see why you want to use JNI to accomplish this. You can call
>system processes with something like System.exec if you want to run
>processes on the Host Os. Programs like make and find don't need 'native'
>access, they just need to access the file system in the normal java way.
There are two very different sides to JNI. I'm thinking of the Invocation
API. You're thinking of the native method API. I want to use the Invocation
API in a Linux program.
The Invocation API is used to start one or more Java virtual machines. A
Java-enabled browser is expected to use the JNI to start applets. The
Netscape Navigator browser, for example, uses the Invocation API to create
a virtual machine for your applets.
While the native method API integrates the native OS into the Java
platform, the Invocation API integrates the Java platform into the native OS.
All the tools use the Invocation API: java, javac, javah, javap, javadoc,
rmiserver and servletrunner.
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
