Dear Rony, > concurrency trace: I have no opinion on this feature, although it seems useful for those debugging multi-thread programs, but if it is a „showstopper“ for releasing 5.0.0 I would also tend to think it is better put in the pipeline for 5.0.1. But only if it is REALLY a hindrance to release 5.0.0, which I think should take place asap. As I understand the discussion there are no other real showstoppers left? > extract and commit the CMake definitions from Enrico's patch to allow ooRexx > on MacOS to be optionally built as a universal binary such that ooRexx can > run with the same binary on Intel and M1 computers. I am also not a fan of overcomplicating things (2 dedicated ooRexx installers for Intel/M1 would be easier to maintain IMO) but if it is the wish of the community to have „fat“ installers I can work with you to get this into the pipeline, but just not at the moment, I am only in Berlin for a couple of days and then off again. Mid October I can do some things. At the moment I have no M1 to test things on BTW, it would be great to have that for Jenkins.
/P.O. > > _______________________________________________ > 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
