FYI, did create ooRexx from trunk (r12104) and created zip-archives ("stick")
from the bin and lib
directories as well, such that ooRexx users like Simon become able to get to
the latest, running
version of ooRexx on their platform. My answer includes the directions, which
are hopefully
clear/understandable.
---rony
P.S.: As I needed the latest ooRexx for an upcoming version of BSF4ooRexx I
also created deb, rpm
installation packages for 32- and 64-bit for Linux in addition to the Windows
versions (installer
and "stick" archive). You can get it temporarily from my DropBox link
<https://www.dropbox.com/sh/a86bt042pravm5p/AADK9Fac5pobhscxKxrRRxkua?dl=0>.
On 20.08.2020 20:27, Rony G. Flatscher wrote:
> It seems to be the case that people hit
> <https://sourceforge.net/p/oorexx/discussion/general/> which
> is not a mailing list, unfortunately.
>
> Only learned by chance (read the latest activities on the Sourceforge
> homepage) that there was a
> posting there today:
> <https://sourceforge.net/p/oorexx/discussion/general/thread/1ea0b2be59/>. Not
> sure what to answer.
>
> My take would be to create a plain zip-archive containing the "bin" and "lib"
> folders on Unix, and
> the "ooRexx" installation folder content on Windows and make them available
> for download along the
> installation packages of ooRexx on the Sourceforge site. Maybe this can be
> done in CMake already
> somehow?
>
> What do you think?
>
> ---rony
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
