javah produces C header files and C source files from a Java class. These files provide the connective glue that allow your Java and C code to interact.
javah [ options ] fully-qualified-classname. . .
javah generates C header and source files that are needed to implement native methods. The generated header and source files are used by C programs to reference an object's instance variables from native source code. The .h file contains a struct definition whose layout parallels the layout of the corresponding class. The fields in the struct correspond to instance variables in the class.
The name of the header file and the structure declared within it are derived from the name of the class. If the class passed to javah is inside a package, the package name is prepended to both the header file name and the structure name. Underscores (_) are used as name delimiters.
By default javah creates a header file for each class listed on the command line and puts the files in the current directory. Use the -stubs option to create source files. Use the -o option to concatenate the results for all listed classes into a single file.
The new native method interface, Java Native Interface (JNI), does not require header information or stub files. javah can still be used to generate native method function proptotypes needed for JNI-style native methods. javah produces JNI-style output by default, and places the result in the .h file.
.;<your_path>For example:
.;C:\users\dac\classes;C:\tools\java\classes
As a special convenience, a class path element containing a
basename of * is considered equivalent to specifying a
list of all the files in the directory with the extension
.jar or .JAR (a java program cannot tell
the difference between the two invocations).
For example, if directory foo contains
a.jar and b.JAR, then the class path
element foo/* is expanded to a
A.jar:b.JAR, except that the order of jar files is
unspecified. All jar files in the specified directory, even hidden
ones, are included in the list. A classpath entry consisting simply
of * expands to a list of all the jar files in the
current directory. The CLASSPATH environment variable,
where defined, will be similarly expanded. Any classpath wildcard
expansion occurs before the Java virtual machine is started -- no
Java program will ever see unexpanded wildcards except by querying
the environment. For example; by invoking
System.getenv("CLASSPATH").
.;C:\users\dac\classes;C:\tools\java\classes
