Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Just for the record: Enrico wrote that the empty post was unintentional and regarding the drag packages and "rexx -v": > What is needed to create the "drag and drop packages"? > Just run cmake with  -DBUILD_DMG=1 After that in the build directory  ./build_macOS_dmg.sh I

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Hi Enrico, it seems that your posting from yesterday does not carry any new text of yours? ---rony On 09.06.2021 16:41, Enrico Sorichetti via Oorexx-devel wrote: > > >> On 9 Jun 2021, at 15:51, Rony G. Flatscher > > wrote: >> >> Enrico, >> >> just two quick

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

> On 9 Jun 2021, at 15:51, Rony G. Flatscher wrote: > > Enrico, > > just two quick questions inline, if you get some time on your hands: > > On 08.06.2021 00:41, Enrico Sorichetti via Oorexx-devel wrote: >> >>> only installs once or a few times so I don’t see a benefit in spending >>>

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Enrico, just two quick questions inline, if you get some time on your hands: On 08.06.2021 00:41, Enrico Sorichetti via Oorexx-devel wrote: > >> only installs once or a few times so I don’t see a benefit in spending >> developers time in making >> big beast. > > I would not call adding from 6

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

> only installs once or a few times so I don’t see a benefit in spending > developers time in making big beast. I would not call adding from 6 to 12 lines of code to the cmakelists a big effort 6 for the simple task of adding the universal build and backwards compatbility to high sierra

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

> Am 07.06.2021 um 18:11 schrieb Rony G. Flatscher : > > The reason why I came up with the question right now is a student who has a > physical new M1 and gets into troubles when running BSF4ooRexx from the Intel > version with Java that got compiled for M1 it seems. > > Hi Rony, I do not

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

It appears that both intel and arm (by default) are little endians. arm V8 can be configured to be both. Sent by Magic! > On Jun 7, 2021, at 8:34 AM, Rick McGuire wrote: > >  > > >> On Mon, Jun 7, 2021 at 10:38 AM CV Bruce wrote: >> Now that I think about it rexx.img was the primary

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Buona sera Enrico, On 07.06.2021 17:26, Enrico Sorichetti via Oorexx-devel wrote: > BTDTGTTS ( Been There Done That Got The Tee Shirt ) > At the beginning of March I made a post  > > > > I built the APPLE ooRexx universal binaries and the test suite runs > > well down to El

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Thank-you Enrico. I guess I missed it. Thanks. Sent by Magic! > On Jun 7, 2021, at 8:43 AM, Enrico Sorichetti via Oorexx-devel > wrote: > >  > BTDTGTTS ( Been There Done That Got The Tee Shirt ) > At the beginning of March I made a post > > > > I built the APPLE ooRexx universal

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

BTDTGTTS ( Been There Done That Got The Tee Shirt ) At the beginning of March I made a post > > I built the APPLE ooRexx universal binaries and the test suite runs > well down to El Capitan > ( both the x86_64 and the apple silicon builds)> > to run the multi arch,

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Rick, thanks for keeping me honest. Sent by Magic! > On Jun 7, 2021, at 8:34 AM, Rick McGuire wrote: > >  > > >> On Mon, Jun 7, 2021 at 10:38 AM CV Bruce wrote: >> Now that I think about it rexx.img was the primary problem. It contains >> executable code, but is not in a library format.

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

On Mon, Jun 7, 2021 at 10:38 AM CV Bruce wrote: > Now that I think about it rexx.img was the primary problem. It contains > executable code, but is not in a library format. You can’t even combine x86 > and amd64 into one binary. > I contains no native code, only core classes and and methods that

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

One could put multiple copies of oorexx into the .dmg file, and then let the installer select the correct/best binary to install. Sent by Magic! > On Jun 7, 2021, at 7:37 AM, CV Bruce wrote: > > Now that I think about it rexx.img was the primary problem. It contains > executable code, but

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Now that I think about it rexx.img was the primary problem. It contains executable code, but is not in a library format. You can’t even combine x86 and amd64 into one binary. There was probably a good reason why rexx.img was implemented (speed or space?). Perhaps it’s time to talk about

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

I suspect rexx.img would not be compatible between the two because of endian issues. Rick On Mon, Jun 7, 2021 at 10:23 AM CV Bruce wrote: > The last time I looked at this, probably ppc/x86, it wasn’t possible > because Rexx is invoked during the build. There are tools to combine > single

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

Bruce, thank you very much for your insights! So then maybe one would need two separate builds on each architecture and then maybe create optionally with "lipo" the fat binaries for each dylib. For this it would be handy to have "stick" versions of ooRexx be buildable, because then one could

Re: [Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

The last time I looked at this, probably ppc/x86, it wasn’t possible because Rexx is invoked during the build. There are tools to combine single binaries into “universal” binaries, but what your are really asking is can OORexx be cross compiled for a non-native architecture. Even then there

[Oorexx-devel] Question ad CMake and "fat binaries" for MacOS

As Apple has been selling new hardware with a proper processor, it would be important to support that hardware platform. In the past Apple allowed for "fat binaries" which included binaries for different hardware architectures in the same file. Would it be possible with CMake to have such