Dear P.O.,
On 17.08.2020 22:51, P.O. Jonsson wrote:
>>
>> Question ad Apple/Mac (Darwin)
>>
>> CMakeLists.txt overrules the CMake default and explicitly installs to
>> "set
>> (CMAKE_INSTALL_PREFIX $ENV{HOME}/Applications/ooRexx${ORX_MAJOR}" (cf.
>> CMakeLists.txt, line #
>> 247. This means that no system wide installation of ooRexx is done.
>>
>> Question 2 (Apple question): should the default installation be to
>> /usr/local, such that by
>> default a system wide installation takes place like on Linux?
>>
> Personally I think */usr/local* would be illogical for macOS (DARWIN). On
> macOS there is no need
> to „install“ ooRexx 5. Thanks to Enrico it can run from anywhere without any
> installation step.
> For this reason I think it would make sense to treat it as any other „App“ on
> macOS.
>
> The current agreement is to put the ooRexx 5 package in the users
> Applications directory
> *~/Applications* (in my case in /Users/po/Applications), this comes with some
> disadvantages:
> (i) the user may need to create ~/Applications (it is not there on a pristine
> system)
> (ii) the user need to amend the path
> (iii) the installation is for that one user only.
> (iv) to uninstall ooRexx the path needs to be restored again
>
> My proposal would be to put the installation in */Applications*, where
> virtually all applications
> reside that are installed by the user. This would mean that all disadvantages
> (i)-(iv) would go
> away automatically.
>
> It would further provide a well recognized method of installing/uninstalling,
> a simple drag&drop
> to the garbage bin would be sufficient to remove every trace of ooRexx. Since
> /Applications is
> already in the path also the man pages work as expected.
>
> I have already made a post-build script (driven by Cmake) that produces a dmg
> installer that looks
> exactly like the installers provided by any regular „app“, with the familiar
> drag&drop
> functionality, also including the documentation, license etc. If there is an
> interest I can show a
> mockup (I do not have access to the real thing from where I am now).
Yes, this would be much better IMHO!
Do you distinguish between "/Library/Frameworks" and "/Applications" locations
as the Apple
developer guide suggests?
The "/Library/Frameworks/ooRexx.framework" locations should be used for the
binaries and include
files (e.g. "ooRexx.framework/Versions/A/Libraries/librexxapi.3.dylib" ...
"ooRexx.framework/Versions/A/Headers/oorexxapi.h"
..."ooRexx.framework/Versions/A/Commands/rexx"...). Then link "Libraries" to
"Versions/Current/Libraries" and the like for "Commands", "Headers", "Shared".
The binaries should then be linked to "/usr/local/bin" and the libraries to
"/usr/local/lib" which
makes them systemwide available, hence ooRexx can be deployed from everywhere.
The "/Applications" directory would contain some "ooRexx.app" folder, but would
need some program
that offers a GUI via which one e.g. could get access to the sample and pdf
help files.
---
If the official ooRexx gets installed into /Library/Frameworks" I could adapt
the BSF4ooRexx
installer for Mac to then only install the "/Applications/ooRexx.app" folder
which I then might
rename to "/Applications/BSF4ooRexx.app". Currently BSF4ooRexx includes ooRexx
as in the past there
was no working ooRexx installation package anymore, it includes a small Java
application which
creates the Mac menu bar with all sorts of folders and programs (comparable to
Windows), such that
the sample and pdf help files become easily accessible by the users.
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
