JNI Generator

Purpose & User Intent: This tool generates standardized JNI scaffolding from Java declarations to support native code integration. Target users are Java and Android NDK engineers, library authors, and automation pipelines requiring repeatable JNI bindings. It reduces boilerplate, enforces correct signatures, and accelerates prototyping of cross-language interfaces. Core Logic & Features: Validate data, map types, generate JNI signatures, and emit a cohesive C/C++ file set. Requires a Java class and a native method list. Outputs include headers, sources, and Java stubs. Optional templates cover JNI_OnLoad and reference handling; multi-file outputs and version-specific templates are supported.

Inputs & Outputs: Inputs include class name, package, native methods (name, return type, parameter types), and JNI version. Outputs are source and header files with native implementations, Java stubs, and minimal build guidance compatible with CMake or ndk-build. Algorithms & Calculations: Type mapping uses Java-to-JNI rules (int -> jint, long -> jlong, String -> jstring). Prototypes follow JNIEXPORT JNICALL and the naming scheme Java_package_Class_method, with overloads suffixed by parameter signatures. Optional templates provide JNI_OnLoad, error checks, and global reference scaffolding.

Error & Edge Cases: Missing class or method definitions trigger explicit errors. Unsupported parameter types produce warnings or rejections. If file writes fail, the tool reports non-fatal errors and outputs the artifacts that could be generated. Industry/Region & Localization: Aligns with Java SE JNI specifications and Android NDK conventions; uses UTF-8 for string literals and standard C/C++ types.

Assumptions & Exclusions: Requires Python runtime and input data. Excludes full build orchestration, runtime linking, and bindings beyond C/C++ JNI scaffolding. Focuses on scaffolding and verification rather than deployment.