[Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

Creating ooRexx from trunk from scratch into a new (empty) directory, which will create the following rxapi-related files: * ./bin/rxapi * ./bin/librexxapi.5.0.0.dylib * ./bin/librexxapi.dylib -> librexxapi.5.0.0.dylib Then doing a "make install" which will use the created interpreter and

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

> I have just started work on a solution that no longer requires a single > daemon for the platform but rather use a single process per Rexx user. Right > now, I'm working on refactoring the code a bit to make it easier to plug in > different management schemes, and the next step will be to

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

On Sun, Nov 25, 2018 at 11:36 AM Rony G. Flatscher wrote: > Creating ooRexx from trunk from scratch into a new (empty) directory, > which will create the following rxapi-related files: > >- ./bin/rxapi >- ./bin/librexxapi.5.0.0.dylib >- ./bin/librexxapi.dylib ->

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

> Am 25.11.2018 um 18:05 schrieb Rick McGuire ... cut ... >> > > I have just started work on a solution that no longer requires a single > daemon for the platform but rather use a single process per Rexx user. Right > now, I'm working on refactoring the code a bit to make it easier to plug

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

> Am 26.11.2018 um 00:06 schrieb Rick McGuire : > > The approach I am working on does not use ports at all. This should get > around a lot of the issues with the current setup. That would be really *great*! —-rony Rony G. Flatscher (mobil/e) ___

[Oorexx-devel] Installers for ooRexx on macOS

Dear all, This is just to inform that I have updated my standalone installers for ooRexx 5.0.0 on Mac, they can be found here: https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0 There is one

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

The approach I am working on does not use ports at all. This should get around a lot of the issues with the current setup. Rick On Sun, Nov 25, 2018 at 6:05 PM Rony wrote: > Thank you very much, will test it tomorrow when back at the office! > > One question: would it also be possible to use a

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

I need someone to do a little more than test it. I can write most of the code, but cannot compile or debug it. If you can do nothing more than try to build it for me once I have the Linux code written, that would be great. Rick On Sun, Nov 25, 2018 at 6:08 PM Rony wrote: > > Am 25.11.2018 um

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

This should be independent of any particular distro. In theory, what I'm doing should work on any *ix based system. Rick On Sun, Nov 25, 2018 at 6:29 PM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > What Linux distro will You need … > I am pretty comfortable

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

Thank you very much, will test it tomorrow when back at the office! One question: would it also be possible to use a different port in case it got taken, despite it being registered fir ooRexx? Cheers —-rony Rony G. Flatscher (mobil/e) > Am 25.11.2018 um 18:26 schrieb Enrico Sorichetti via

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

> Am 26.11.2018 um 00:13 schrieb Rick McGuire : > > I need someone to do a little more than test it. I can write most of the > code, but cannot compile or debug it. If you can do nothing more than try to > build it for me once I have the Linux code written, that would be great. Sure, I can do

Re: [Oorexx-devel] Question ad CMake and MacOS ("rxapi" related)

What Linux distro will You need … I am pretty comfortable running centos if that is enough Enrico > On 26 Nov 2018, at 00:26, Rony wrote: > > >> Am 26.11.2018 um 00:13 schrieb Rick McGuire : >> >> I need someone to do a little more than test it. I can write most of the >> code, but cannot