Hello everybody,
where to install things almost always resulted in a flame war,
I speak for the *ix side…
why not leave things as they were once upon a time ???
intall to /opt/oorexx if nothing is specified
the advantage is that no root priviliges are needed
no issues about the <lib> subdirectory
after that the user has the most freedom,
create the links from wherever he/she chooses
or - cleaner IMO - add a couple of lines to the profile
to dynamically add the ooRexx install path to the PATH directory
a welcomed addition would be the installation of oorexx.pc the
pkg-config/pkgconf data
that people who want to link against the oorexx libraries will not have the
need to specify everything by hand
after that the CMakelists coding can be the same fo any *ix like system
the only distinction would be for the RPATH specification
for apple is done with @loader_path/@executable_path. ( still experimenting
which token is best )
while for a generic *ix is done with $origin
I am experimenting with it in my linux and freebsd vagrant boxes
as far portability ( usb stick ) the ground is a bit murkier …
no issues for the .so’ and the .dylib’s
the are a couple of quirks in the search for the rexx image
it searches in the PATH and not where it should
IMO - the same directory of the executable
but again, dynamically mangling the PATH will fix things
sidenote…
a few emails ago i was complaining about spurious abends, the above was the
reason,
I was invoking rexx with the full executable path
and my copy of rexx was using everything from the rexx installed in the PATH
I have the same concerns for the catopen
stiil trying to understand the catopen search logic
from my understanding nothing of the above happens on windows
everything is taken from the path where the executable resides
as far as the distributing the executables
I would not worry about creating the debs/rpms
especially if we choose to go bak to the old times and install to /opt/oorexx
my understanding is that the developers of the various linux distributions
will have to adapt the installers to the linux install tool (yum,dnl,apt,…,…,… )
and will anyway rewrite the installer
for an independent install I think that a tgz/zip should be more than enough
sorry for the long email
Easter greeting to everyone
enrico
PS…
do we really need the complication of the COMPONENT things ?
with the CMAKE componentization looks like that every component is put in a
different tgz file
when I got rid of the COMPONENT construct only one tgz was created
( empty but just one :-( )
the test were very quick and very dirty
in a few days will try to do thing with a bit more of method
PS**2 .
sorry for my english, it is not as it was once
lately I have been speaking more french than english
> On 29 Mar 2018, at 00:36, P.O. Jonsson <[email protected]> wrote:
>
> Dear Erich,
>
> I have had some progress lately.
>
> 1. I have a complete HowTo to be put on the WIKI for Mac users. I am now
> confident in building ooRexx manually for the Mac. It will need an adaptation
> of the CMakeLists.txt I will propose the changes later. Basically it is what
> Enrico proposed earlier (so as to be able to redirect the build path at the
> command line).
>
> 2. I have failed to make a proper installer for the Mac although I know it
> must be possible (because Rony have done it). I have put that on halt, maybe
> someone with more knowledge can do it proper. There is currently NO working
> ooRexx installer for Mac besides the (very good) installer with Bsf&ooRexx
> combo.
>
> 3. Instead of a proper installer I have done the 2nd best, I have written an
> installer script that can convert a manual installation built previously to a
> permanent installation, with symlinks in all the right places. Even the man
> pages work. The layout is slightly different from what the BSF/ooRexx
> installer produces but they seems to function in the same manner. Having made
> a local build I can package this in a dmg file for use by others. But it must
> be used from the command line.
>
> I have opted to put the installation in /usr/local/oorexx5.0.0 and make
> symlinks to /usr/local/bin,lib,include and the man pages.
> I have, at the same time, made an uninstaller that completely wipes the
> installation of the machine.
>
> I need to do some further testing but hopefully I can provide something for
> others to test tomorrow (29th), is there a „sandbox“ available where I can
> put it?
>
> 4. The installer needs superuser rights to install/uninstall to/from
> /usr/local but I was thinking that if one installs in the home directory (or
> even on a USB) it might be possible to make an installation that can be used
> with lesser user rights. Might solve the „run from USB“ problem then, at
> least on a Mac.
>
> 5. If it is decided to freeze a version for making it public I can volunteer
> to try all samples. I can do it on Mac, Windows 7 and 10 (and possibly Win
> XP).
>
> 6. If there is a need I have a spare machine running Win10 to be used by
> Jenkins. Maybe not forever but for at least the coming six months. I could
> set it up for Linux as well if you just tell me what you want on it.
>
> Enjoy Aruba if you go there. Greetings to René as well.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> [email protected] <mailto:[email protected]>
>
>
>
>
>> Am 27.03.2018 um 18:50 schrieb Erich Steinböck <[email protected]
>> <mailto:[email protected]>>:
>>
>> showstoppers in ooRexx 5.0 ?
>>
>> René,
>> except for Windows, Ubuntu, CentOS and a bunch of (now outdated) RPM's built
>> by Erico, we have no builds.
>> Most of the builds we run on Jenkins still don't give access to their built
>> packages
>>
>> Also we have no doc or devel builds for Unix (and I really don't know how
>> these would have to be done)
>>
>> we'll also have to
>> bring CHANGES.txt and ReleaseNotes.txt up-to-date
>> verify that all provided samples work as expected. On Windows I noticed
>> that many of the oodialog samples (e. g. AnimalGame or oobandit) fail
>>
>>
>> On Fri, Mar 23, 2018 at 12:34 AM, [email protected]
>> <mailto:[email protected]> <[email protected] <mailto:[email protected]>>
>> wrote:
>>
>> Hi ooRexx developers,
>>
>> As we have the symposium next week the question pops up (like it did last
>> year), if ooRexx 5.0 is ready to be released. In other words, are there real
>> showstoppers in the recent revisions?
>>
>> I am sure we are all aware that it is quite some time since we released an
>> official version. Wikipedia puts it at 4 years ago.
>>
>> There are some things I can think of:
>> - ooDialog
>> - the portable ‘usb’ version
>> - installer for macos
>> - recent performance increases
>>
>> but personally I think it is fine if these land in 5.1; I do not have an
>> opinion at all on ooDialog.
>>
>> Would it be a bad idea to freeze a revision one of these days, have a close
>> look at it,and try to bring it to GA.
>>
>> Who thinks we still have showstoppers in ooRexx 5.0 ?
>>
>> Best regards,
>>
>> René.
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>> http://sdm.link/slashdot <http://sdm.link/slashdot>
>> _______________________________________________
>> Oorexx-devel mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>> http://sdm.link/slashdot_______________________________________________
>> <http://sdm.link/slashdot_______________________________________________>
>> Oorexx-devel mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
