Go ahead and take a crack at it, but I seriously doubt it will work. Mike's
solution works because he only has to worry about a single executable. In
the ooRexx case, we would need to insert this logic into both rexx.exe and
rexxhide.exe, and have the logic to handle every single one of the binary
artifacts of a release, including multiple dlls and the rexx.img binary
image. Not really practical.

Rick

On Tue, Apr 12, 2022 at 10:26 AM P.O. Jonsson <oor...@jonases.se> wrote:

> On the RexxLa <rexxla-memb...@groups.io> list it was noted that we have 8
> different installers for Windows, which is a bit confusing. Since it
> appears that windows.x86_32.exe and windows.x86_64.exe work on all Windows
> 7/8/10 platforms I suggest to stop uploading the additional installers
> built on W7/W8.1/W10 Virtual Machines.
>
> I still  think we should continue building & testing on those platforms.
>
> Mike Cowlishaw offered a solution for a single installer for 32/64 bit
> Windows in that thread
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to