On 19.07.2021 17:13, P.O. Jonsson wrote: > Ok, so I checked rev 12280 on some Linux installations (Raspberry Pi, Debian, > Linux Mint, Fedora, > CentOS) and they all show the same 2 CallRexx and 3 Libwpipe files in the > installed /bin > directory, so it is not just macOS/Darwin thingy, it is a generic fault (if > it is a fault) for the > *nixes. > > I could not find oorexx-config in ANY installation so I guess this is a local > file on Rony´s > computer, maybe from the „fat binary“ exercise? It is not present in any of > the installations I > looked at. None.
Yes, now I recall: this was a file that Enrico sent with a minimized (cleansed) version of the Makefile to create a fat BSF4ooRexx library. (Actually, I updated the older Makefile and use that as it does not have a dependency on oorexx-config. As I rarely have to compile BSF4ooRexx.cc I keep forgetting such dependencies myself which causes some time-losses and frustrations on my side on a regular basis. :) ) > Windows is entirely different from the rest of the installations and there > are some Callrxnt.exe > etc files in the installed ooRexx (I only looked at the 64-bit version) but I > must assume that > they are intentionally there since the Windows installer is /properly/ using > CMakelists.txt, right? Whenever an overhaul of CMake is in the works one thing I would like to propose is to also allow for creating a "stick" version of the ooRexx interpreter and make that downloadable as well. It would have the benefit that anyone interested can download it and get it running on the target system without installation. (A first excercise in that direction was done for last year's Rexx symposium. It would use an already installed version of ooRexx and with the help of a little Rexx script create a stick version of the Windows, Linux and MacOS version.) ---rony
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
