Just for the record: Enrico wrote that the empty post was unintentional and
regarding the drag&drop
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 am almost done with ….
rexx -e "say .RexxInfo~processor"
arm64
And with
rexx -v
Open Object Rexx Version 5.0.0 r12266
Build date: Jun 7 2021
Build mode: arm64.universal, 64 bits
I just have to check the cross builds and backward portability
---rony
On 10.06.2021 08:54, Rony G. Flatscher wrote:
>
> 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 <rony.flatsc...@wu.ac.at
>>> <mailto:rony.flatsc...@wu.ac.at>> 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
>>>>> 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
>>>> around 6 more lines if you want to inform the user about the arch and the
>>>> universal build
>>>> when issuing *rexx -v
>>>> *
>>>
>>> What would these lines look like? :)
>>>
>>>
>>>> and you do not need to build two different drag and drop packages
>>>> also you can build from a x86_64 machine the universal for the arm64
>>>
>>> What is needed to create the "drag and drop packages"?
>>>
>>> TIA,
>>>
>>> ---rony
>>>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
