As rexx.img must be of the same architecture, bitness and endianness it is not possible to use a
single rexx.img for different architectures, bitnesses and endiannesses.
The present packaging and installation of ooRexx can therefore not take advantage of universal
packages available on macOS (because of rexx.img) such that we should start to stop producing the
universal macOS version and instead have two different macOS packages created, one for amd64 and one
for arm64.
---
As rexx.img gets installed into and loaded from the lib directory as if it was a native library,
would it make sense to think of a universal packaging format for rexx.img which would allow to
create a form of universal rexx.img? E.g. a table that indicates the available architectures and
positions in a rexx.img file such that ooRexx can pick the appropriate version?
If so, then it would be probably be helpful to allow for universal user compiled Rexx programs as
well, as the same infrastructure could then be put in place, if not mistaken.
What do you think would such an endeavor be worthwhile at all?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
