> Danny, are you volunteering to implement Cmake or Meson for the non-ksh93 > code?
Sorry, I don't have the free time at my disposal and it probably is a *lot* of work for little gain and that would take away from ksh development itself, which is why my proposal was to separate it out and leave it as is. Anyway, I thought I would put my proposal out there, but if no-one wants to do it that way, that's fine. Whether the new ast+ksh code then is the new master or a separate repo I don't care, either way. To decrease build times perhaps some work could be done to make the iffe probing be done in parallel. > That is an extremely bold proposal. As you alluded to there is a bit of a > chicken and egg problem. Ksh93 source in its current form cannot be built > independent of large chunks of the AST code base. So to be able to build > just ksh93 you first have to build and package the rest of the AST project > so that it is available to the ksh93 project on Linux, FreeBSD, macOS > (via Homebrew), etc. If someone steps up and does that work that would > be great. The question is whether there is anyone motivated to do that > work. And even if it were done it would make it difficult to modernize > the ksh93 code by removing support for things like K&R compilers. bin/package has some support for building packages but as you say, it would need updating for all those OS's. It doesn't sound too difficult and would be done in lib/package/package.mk. I'm not sure I understand why it would not be possible to remove support for K&R compilers. _______________________________________________ ast-developers mailing list ast-developers@lists.research.att.com http://lists.research.att.com/mailman/listinfo/ast-developers
