Qvar_1Q Qvar_2Q - Qvar_3Q

Qvar_4Q

ooRexx Sources and Links

Open Object Rexx must be compiled from sources provided by Open Object Rexx (ooRexx) website [1]. It is not part of the Packages Collection (pkgsrc) [2, 3]. Beside ooRexx most Rexx scripts can be run with Regina Rexx [4] or REXX/icm [5] wich are included both in pkgsrc [2] and on FTP sites with binery files [3].

[1] Open Object Rexx Downloads
[2] pkgsrc: The NetBSD Packages Collection
[3] Application Software for NetBSD
[4] REXX/imc
[5] Regina Rexx

INSTALL File Remarks

ooRexx compilation is straightforward. Let's quote ooRexx documentation:

Installation Notes for Open Object Rexx
=======================================

Please read ALL of these notes before building ooRexx!

To install ooRexx, you first need to configure it. This is done by executing the configure script provided in this archive.

Generally all you need to run is "configure", but there are some options that can be passed to the configure script; use "configure --help" to view them. If the configure script does not exist then run "bootstrap" script to create it.

Once the configure script has been run, you can then type "make". This will create the following objects:

 rexx            the ooRexx interpreter
 rexxc           the ooRexx "compiler"; it is really a tokenizer
 rxqueue         interface from command line to Rexx queue
 rxsubcom        enables subcommand environments to be manipulated
 rxdelipc        utility to remove IPC objects
 librexx.so      shared library containing majority of interpreter
 librexxapi.so   shared library containing API functionality
 librxmath.so    maths extension library
 librexxutil.so  RexxUtil extension library; system functions
 librxregexp.so  Regular Expression extension library
 librxsock.so    Low-level socket extension library
    

Once you have ooRexx compiled, it can then be installed. By default, the ooRexx executables will be installed into /opt/ooRexx/bin and the libraries and external function packages (*.so) will be installed into /opt/ooRexx/lib/ooRexx. The base path "/opt" can be changed by adding the --prefix=path (where path is the base path) to the configure command. eg. to install ooRexx into your home directory: $HOME/bin and $HOME/lib/ooRexx, configure --prefix=$HOME ... This is paticularly useful if you do not have root access on the machine on which you are building ooRexx.

On most platforms, it is necessary to include the directory where shared libraries (including *.so) reside, to the LD_LIBRARY_PATH environment variable. Under AIX this environment variable is LIBPATH. Under HP-UX this environment variable is SHLIB_PATH. Under SGI seems to be LD_LIBRARYN32_PATH. (...)

Platform Specifc Notes

*BSD Platforms:


ooRexx builds on FreeBSD 5.4 and 6.1, NetBSD 2.0.2 and OpenBSD 3.4. May be a bug due to ooRexx using members of internal C structs which are not portable across platforms.

Compilation Remarks

I've compiled ooRexx with folowing parameter

    # configure --prefix=/usr/pkg
    

and everything went smoothly. It can be compiled from user account and from system directory e.g. /usr/pkg/share/oorexx. Or even /opt/ooRexx but this is not recommended as against NetBSD rules keeping all additional packages (no system apps) within /usr/pkg directory.

Another commands that must be issued are:

    # make
    # make install
    

As all rexx versions and variants, also ooRexx is provided with /samples directory with scores of example scripts.

ATTENTION
ooRexx libraries are gathered in /usr/pkg/lib/ooRexx. In the case when "something" worked wrong the libs might be symlinked into /usr/pkg/lib directory (parent to ooRexx).