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. 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? Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 16.07.2021 um 18:04 schrieb Rick McGuire <object.r...@gmail.com>: > > btw, if you were properly using the information from CMake.txt to build the > .dmg, you would not be having this problem, since all of the install() > statements identify which elements of the build should go where. That > information is used by all of the other installer types (including the > Windows one, which is done without CMake builtin CPack support).
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
