fpc/utils/pas2jni
2014-02-07 12:37:17 +00:00
..
def.pas
fpmake.pp * Handle the location of each package at run-time, not at compilation time 2013-06-02 17:55:23 +00:00
Makefile * mipsel-android: Regenerated makefiles. From now the mipsel-android target can be built and used. 2014-02-07 12:37:17 +00:00
Makefile.fpc * always use forward slashes in path to fpmake similarly to paths to other tools in Makefiles 2014-02-01 00:11:09 +00:00
Makefile.fpc.fpcmake * Switched utils to fpmake building 2013-05-26 19:05:11 +00:00
pas2jni.pas * Removed unneeded {$apptype console}. 2013-04-03 19:42:43 +00:00
ppuparser.pas * pas2jni: fixed error during records processing. 2013-05-15 15:58:27 +00:00
readme.txt
writer.pas * pas2jni: fixed processing of int64 and boolean constants. Also fixes to correctly process whole System unit. 2013-05-15 15:34:10 +00:00

pas2jni - JNI bridge generator for Pascal.

Copyright (c) 2013 by Yury Sidorov.

The pas2jni utility generates a JNI (Java Native Interface) bridge for a Pascal code. Then the Pascal code (including classes and other advanced features) can be easily used in Java programs.

For example you can do the following in Java:

import pas.classes.*;

...

TStringList sl = TStringList.Create();
sl.Add("Hello.");
String s = sl.getStrings(0);
sl.Free();

...

The following Pascal features are supported by pas2jni:

- function/procedure;
- var/out parameters;
- class;
- record;
- property;
- constant;
- enum;
- TGuid type;
- pointer type;
- string types;
- all numeric types;

Shared libraries, generated by pas2jni were tested with Java on Windows and Android. It should work on other systems as well.

HOW TO USE

pas2jni uses the ppudump utility included with Free Pascal Compiler to read unit interfaces. Therefore your Pascal code must be first compiled with FPC.
When your units are compiled, you can run pas2jni. You need to specify a list of main units and units search path. 
When you specify a main unit, all its interface declarations will be available in Java. For linked units only used declarations will be available. You can fine tune included/excluded declaration using -I and -E command line options.

The basic invocation of pas2jni:

pas2jni myunit -U/path/to/my/units;/path/to/FPC/units/*

Here you specify myunit as the main unit and provide path to your compiled units and FPC compiled units. 

After successfull run of pas2jni you will get the following output files:
- file "myunitjni.pas" - a generated library unit to be compiled to a shared library. It will contain all your Pascal code to be used from Java.
- folder "pas" - generated Java package "pas" to be used in your Java program. Interface to each Pascal unit is placed to a separate Java public class. 

Note: You need to use ppudump of the same version as the FPC compiler. Use the -D switch to specify correct ppudump if it is not in PATH.

COMMAND LINE OPTIONS

Usage: pas2jni [options] <unit> [<unit2> <unit3> ...]

Options:
  -U<path> - Unit search path, semicolon delimited. Wildcards are allowed.
  -L<name> - Set output library name.
  -P<name> - Set Java package name.
  -O<path> - Set output path for Pascal files.
  -J<path> - Set output path for Java files.
  -D<prog> - Set full path to the "ppudump" program.
  -I<list> - Include the list of specified objects in the output. The list is
             semicolon delimited. To read the list from a file use -I@<file>
  -E<list> - Exclude the list of specified objects from the output. The list is
             semicolon delimited. To read the list from a file use -E@<file>
  -?       - Show this help information.