| 1 |
This file describes how an author of a Rexx external function package |
| 2 |
needs to alter their package to be supported by Regina. |
| 3 |
|
| 4 |
o The external package needs to be provided as a statically linkable library. |
| 5 |
Under Unix platforms, this is usually built with the "ar" command, and has |
| 6 |
a name of "libpackage.a", where "package" is the package name. |
| 7 |
o You need to include in the library a function: |
| 8 |
void *getpackageFunctionAddress( char *name ); |
| 9 |
where "package" is the package name. |
| 10 |
This function returns the address of the Rexx external function with the |
| 11 |
name "name". The comparison between "name" and the function name within |
| 12 |
the package should be done irrespective of case. |
| 13 |
Note that the address of the package's "load" function; eg SysLoadFuncs, must |
| 14 |
be returned with a call to this function. |
| 15 |
See the included test1 and test2 external function packages (test1.c and |
| 16 |
test2.c). |
| 17 |
o Changes are also required to Regina; staticld.c and the aclocal.m4 autoconf |
| 18 |
file. See the other supported external function packages for what to |
| 19 |
include. |
| 20 |
|
| 21 |
To build a "regina" binary that contains multiple, statically linked external |
| 22 |
function packages follow these steps. |
| 23 |
|
| 24 |
1) Build Regina normally without any statically loaded external function packages. |
| 25 |
2) Install this build |
| 26 |
3) Build each external function package normally |
| 27 |
4) Configure Regina to include the external function packages required and build |
| 28 |
5) Do NOT install this version of Regina as the regina-config file will return |
| 29 |
a list of all static libraries that the "regina" binary was built with and |
| 30 |
next time you try and build one external function package it will attempt to |
| 31 |
link in all the others. Simply copy the build "regina" binary as required. |