Dave,
thank you very much for your feedback!
Ad BSF4ooRexx, see below.
On 03.02.2022 16:07, Dave Jones wrote:
> Hello, Rony.
> Thanks for sharing your "portable" ooRexx and BFS4ooRexx .zip files. I've
> downloaded them and installed both here on my openSuSE Tumbleweed Linux
> laptop. They both installed without any serious problems ( for BFS4ooRexx I
> did have to create a specific group that did not exist here). I would vote to
> make this part of the official distributions.
>
> Now I am trying to use ooRexx and BFS4ooRexx to build Linux Rexx apps with
> GUIs. I've run into a problem that I can't figure out how to fix and I'm
> hoping someone with more Java experience than I have (== 0) can help me out.
> Running /home/dave/Desktop/bsf4oorexx/samples/1-030_JavaVersion.rxj, I get:
> Error 40 running /home/dave/Desktop/bsf4oorexx/samples/1-030_JavaVersion.rxj
> line 36: Incorrect call to routine.
> Error 40.900: BSF4ooRexx/routine/BsfLoadJava(), error 5.994: initialization
> error, cannot find class 'org/rexxla/bsf/engines/rexx/Java4Rexx'.
> Is there something wrong/missing with my environment setup?
Yes, CLASSPATH is not set such that the needed Java class cannot be found. This
is what you should
do after unzipping the package:
* change into "bsf4oorexx/install"
* run "rexx setupBSF.rex": this will create various scripts among them
"rexxj.sh" and
"setEnvironment4BSF.sh"
o use "rexxj.sh" to run the scripts, e.g. "rexxj.sh
1-030_JavaVersion.rxj"
o use "setEnvironment4BSF.sh" to set your shell's environment such that
you can run the
BSF4-ooRexx programs.
HTH,
---rony
P.S.: Currently working also on a "portable BSF4ooRexx", but will take a while.
It is meant to be
structure and use as the "portable ooRexx" version.
>
> On Tue, 1 Feb 2022 14:49:16 +0100, "Rony G. Flatscher"
> <rony.flatsc...@wu.ac.at> wrote:
>
>> Inspired by Java/OpenJDK zip archives I tried to create "portable" versions
>> of ooRexx. Once
>> unzipped, there is a simple, uniform directory layout that is the same for
>> all operating systems
>> (bin, doc, include, lib, samples).
>>
>> In addition the unzipped directory includes a utility named
>> "setupoorexx.{cmd|sh}" and if run,
>> creates two shell scripts, a "rxenv.{sh|cmd}" and "setenv2rxenv.{sh|cmd}"
>> which point/refer to the
>> local, unzipped ooRexx.
>>
>> This way one can easily have a number of different "potable" ooRexx
>> interpreters with different
>> revisions, bitnesses, release and debug versions that can be run/tested at
>> the same time on the same
>> machine (e.g. for development or testing or demonstration purposes).
>>
>> It would be possible to carry those portable ooRexx interpreters on an USB
>> stick (and run them from
>> there on any operating system after running the setupoorexx shell script) or
>> to place them on a
>> local network or even to attach them to a mail.
>>
>> The cmake driven operation will create two versions, a full version and a
>> runtime version (the
>> runtime version does not include the doc and samples directories).
>>
>> The scripts generated with "setupoorexx.{sh|cmd}" make it easy to run Rexx
>> programs without having
>> ooRexx installed on a target system.
>>
>> ---
>>
>> To see or test for yourself you may use this temporary Dropbox link:
>> <https://www.dropbox.com/sh/n65twckpkixl9gm/AADrnjgHAqiWQQU17GjGrtpna?dl=0>
>> which used the latest
>> version of ooRexx 5.0 from trunk for Apple, Linux and Windows.
>>
>> Its content is:
>>
>> Directory of e:\Dropbox\portable\release
>>
>> 01.02.2022 14:17 <DIR> .
>> 01.02.2022 14:17 <DIR> ..
>> 30.01.2022 18:59 1 833 594
>> ooRexx-5.0.0-darwin64-r12352-universal-portable-release-runtime.zip
>> 30.01.2022 18:59 11 446 653
>> ooRexx-5.0.0-darwin64-r12352-universal-portable-release.zip
>> 01.02.2022 14:06 1 420 066
>> ooRexx-5.0.0-linux64-r12352-x86_64-portable-release-runtime.zip
>> 01.02.2022 14:06 11 022 636
>> ooRexx-5.0.0-linux64-r12352-x86_64-portable-release.zip
>> 30.01.2022 13:24 1 439 030
>> ooRexx-5.0.0-win32-r12352-x86_32-portable-release-runtime.zip
>> 30.01.2022 13:24 21 009 536
>> ooRexx-5.0.0-win32-r12352-x86_32-portable-release.zip
>> 30.01.2022 14:10 1 636 074
>> ooRexx-5.0.0-win64-r12352-x86_64-portable-release-runtime.zip
>> 30.01.2022 14:10 21 210 870
>> ooRexx-5.0.0-win64-r12352-x86_64-portable-release.zip
>> 8 File(s) 71 018 459 bytes
>>
>> Directory of e:\Dropbox\portable\release\debug
>>
>> 01.02.2022 14:17 <DIR> .
>> 01.02.2022 14:17 <DIR> ..
>> 30.01.2022 18:59 2 638 395
>> ooRexx-5.0.0-darwin64-r12352-universal-portable-debug-runtime.zip
>> 30.01.2022 18:59 12 263 053
>> ooRexx-5.0.0-darwin64-r12352-universal-portable-debug.zip
>> 01.02.2022 14:09 5 899 821
>> ooRexx-5.0.0-linux64-r12352-x86_64-portable-debug-runtime.zip
>> 01.02.2022 14:09 15 625 873
>> ooRexx-5.0.0-linux64-r12352-x86_64-portable-debug.zip
>> 30.01.2022 13:50 7 662 456
>> ooRexx-5.0.0-win32-r12352-x86_32-portable-debug-runtime.zip
>> 30.01.2022 13:50 27 299 302
>> ooRexx-5.0.0-win32-r12352-x86_32-portable-debug.zip
>> 30.01.2022 14:22 8 036 177
>> ooRexx-5.0.0-win64-r12352-x86_64-portable-debug-runtime.zip
>> 30.01.2022 14:22 27 692 923
>> ooRexx-5.0.0-win64-r12352-x86_64-portable-debug.zip
>> 8 File(s) 107 118 000 bytes
>>
>> You will notice the differences in size depending whether it is the debug or
>> the release version and
>> depending whether it is the full or the runtime version.
>>
>> ---
>>
>> If you can see utility in this, then I am more than happy to commit the
>> necessary changes to the
>> project such that one simply needs to issue "make portable".
>>
>> You can download any of the above portable zip archives for your operating
>> system, unzip them, run
>> the setupoorexx shell scripts and study the readme.txt output.
>>
>> ---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
