Dear P.O.,
On 06.02.2020 13:03, P. O. Jonsson wrote:
>
> https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0
>
thank you very much, looks really great!
You have managed to create a dmg installer and even give directions on how to
use that ooRexx 5.0 on
MacOS on an USB-stick!! Really well done, thank you very much for sharing!
Ad harddisk installation and the directions where to add the export PATH
statement with
~/Application/ooRexx5 where the latest MacOS ("Catalina") seems to have
switched from bash to zsh.
The environment variable SHELL should indicate the shell in use on the system,
such that it is
perhaps possible to write a little script that appends that path to the rc file
in the user's directory.
Please keep up your excellent work!
Best regards
---rony
P.S.: The BSF4ooRexx installation package for Windows and Linux actually also
includes the
installation logic for MacOS, such that it would be possible to have your dmg
to install ooRexx 5.0
and install BSF4ooRexx on top of it. But note: I have not tested it in many
years as there was no
standalone ooRexx5 installer available such that I created that separate
MacOS-BSF4ooRexx installer
that includes ooRexx5.
So once your installer becomes part of the ooRexx build process for MacOS I
will start to test the
MacOS BSF4ooRexx installation part again!
>
> Von meinem iPhone gesendet
>
>> Am 06.02.2020 um 12:54 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>:
>>
>> On 05.02.2020 17:19, P.O. Jonsson wrote:
>>> Renés question made reconsider; I realized that the Disk Utility (diskutil)
>>> can indeed be
>>> scripted on the Mac, as can most things I needed to make an installer.
>>>
>>> I have prepared a dmg installer that looks pretty much like a „real“
>>> DragnDrop MacOS installer.
>>> All additional steps compared to the existing build process are simple
>>> command-line calls that
>>> can be added to the current build process on Jenkins. I have used a utility
>>> called fileicon
>>> <https://github.com/mklement0/fileicon> to handle the icon but everything
>>> else is basic unix
>>> shell commands. Most certainly some of these steps can be integrated in
>>> CMakelists.txt later,
>>> but for now this is what you get :-)
>>
>> +1
>>
>>> Please have a look in my Dropbox, the only thing I have not scripted is the
>>> inclusion of a build
>>> nr & a date in the filename, everything else is automated. This installer
>>> was build on High
>>> Sierra (10.13) but run on Mojave (10.14) with no errors and on Catalina
>>> (10.15) with one error
>>> (separate posting on this later).
>>>
>>> I have included the license and a HowTo in the installer; later it needs to
>>> be discussed what
>>> should go in there, for instance
>>>
>>> CHANGES
>>> CONTRIBUTORS
>>> INSTALL
>>> NOTICE
>>> ReleaseNotes
>>>
>>> From the SVN source, or the PDF documentation, that could all be scripted
>>> in the same manner.
>>>
>>> PS attached images seems to be stripped by sourceforge so I have put a
>>> screenshot in my dropbox,
>>> link below still works. Enjoy.
>>>
>> Could you post your Dropbox link?
>>
>> Cheers
>>
>> ---rony
>>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
