On 07.01.2024 20:00, Rick McGuire wrote:
On Sun, Jan 7, 2024 at 1:21 PM Rony G. Flatscher <rony.flatsc...@wu.ac.at>
wrote:
Is rexx.img dependent on the architecture and bitness?
Yes, it contains LOTS of binary data that depends on the bitness of the architecture. There are
some bits that might even be dependent on the compiler used to compile the interpreter that
created the image file.
With other words: can a rexx.img be used at the same time for arm64 and
amd64 (Intel)?
Not a chance.
Thank you for the clarification, Rick!
---
Testing the current beta of ooRexx for the macOS which is a universal package. The binaries are all
universal (both, arm64 and amd64 in one file) such that the loader is able to decide to pick the
version that is appropriate for the platform. "rexx.img" is located in the lib directory
(/usr/local/lib) next to the universal libraries.
So for the macOS universal installer we need to come up with some solution for this problem like
having the installer pick the target platform's rexx.img version. Alternatively, we should not
produce a universal macOS package for ooRexx, but rather have two different installers, one for
amd64 and one for arm64.
What do you think would be the most appropriate approach?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
