gcjh(1) [redhat man page]
GCJH(1) GNU GCJH(1) NAME
gcjh - generate header files from Java class files SYNOPSIS
gcjh [-stubs] [-jni] [-add text] [-append text] [-friend text] [-preprend text] [--classpath=path] [--CLASSPATH=path] [-Idir...] [-d dir...] [-o file] [-td dir] [-M] [-MM] [-MD] [-MMD] [--version] [--help] [-v] [--verbose] classname... DESCRIPTION
The "gcjh" program is used to generate header files from class files. It can generate both CNI and JNI header files, as well as stub implementation files which can be used as a basis for implementing the required native methods. OPTIONS
-stubs This causes "gcjh" to generate stub files instead of header files. By default the stub file will be named after the class, with a suf- fix of .cc. In JNI mode, the default output file will have the suffix .c. -jni This tells "gcjh" to generate a JNI header or stub. By default, CNI headers are generated. -add text Inserts text into the class body. This is ignored in JNI mode. -append text Inserts text into the header file after the class declaration. This is ignored in JNI mode. -friend text Inserts text into the class as a "friend" declaration. This is ignored in JNI mode. -prepend text Inserts text into the header file before the class declaration. This is ignored in JNI mode. --classpath=path --CLASSPATH=path -Idirectory -d directory -o file These options are all identical to the corresponding gcj options. -o file Sets the output file name. This cannot be used if there is more than one class on the command line. -td directory Sets the name of the directory to use for temporary files. -M Print all dependencies to stdout; suppress ordinary output. -MM Print non-system dependencies to stdout; suppress ordinary output. -MD Print all dependencies to stdout. -MMD Print non-system dependencies to stdout. --help Print help about "gcjh" and exit. No further processing is done. --version Print version information for "gcjh" and exit. No further processing is done. -v, --verbose Print extra information while running. All remaining options are considered to be names of classes. SEE ALSO
gcc(1), gcj(1), gij(1), jv-scan(1), jcf-dump(1), gfdl(7), and the Info entries for gcj and gcc. COPYRIGHT
Copyright (C) 2001, 2002 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being ``GNU General Public License'', the Front- Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the man page gfdl(7). gcc-3.2.2 2003-02-25 GCJH(1)
Check Out this Related Man Page
GCJ-DBTOOL(1) GNU GCJ-DBTOOL(1) NAME
gcj-dbtool - Manipulate class file mapping databases for libgcj SYNOPSIS
gcj-dbtool OPTION DBFILE [MORE] ... gcj-dbtool [-0] [-] [-n] [-a] [-f] [-t] [-l] [-p [LIBDIR]] [-v] [-m] [--version] [--help] DESCRIPTION
"gcj-dbtool" is a tool for creating and manipulating class file mapping databases. "libgcj" can use these databases to find a shared library corresponding to the bytecode representation of a class. This functionality is useful for ahead-of-time compilation of a program that has no knowledge of "gcj". "gcj-dbtool" works best if all the jar files added to it are compiled using "-findirect-dispatch". Note that "gcj-dbtool" is currently available as "preview technology". We believe it is a reasonable way to allow application-transparent ahead-of-time compilation, but this is an unexplored area. We welcome your comments. OPTIONS
-n DBFILE [SIZE] This creates a new database. Currently, databases cannot be resized; you can choose a larger initial size if desired. The default size is 32,749. -a DBFILE JARFILE LIB -f DBFILE JARFILE LIB This adds a jar file to the database. For each class file in the jar, a cryptographic signature of the bytecode representation of the class is recorded in the database. At runtime, a class is looked up by its signature and the compiled form of the class is looked for in the corresponding shared library. The -a option will verify that LIB exists before adding it to the database; -f skips this check. [-][-0] -m DBFILE DBFILE,[DBFILE] Merge a number of databases. The output database overwrites any existing database. To add databases into an existing database, include the destination in the list of sources. If - or -0 are used, the list of files to read is taken from standard input instead of the command line. For -0, Input filenames are terminated by a null character instead of by whitespace. Useful when arguments might contain white space. The GNU find -print0 option produces input suitable for this mode. -t DBFILE Test a database. -l DBFILE List the contents of a database. -p Print the name of the default database. If there is no default database, this prints a blank line. If LIBDIR is specified, use it instead of the default library directory component of the database name. --help Print a help message, then exit. --version -v Print version information, then exit. SEE ALSO
gcc(1), gcj(1), gcjh(1), jcf-dump(1), gfdl(7), and the Info entries for gcj and gcc. COPYRIGHT
Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, the Front-Cover Texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the man page gfdl(7). (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. gcc-4.5 2010-07-05 GCJ-DBTOOL(1)