Momtchil Momtchev
Momtchil Momtchev
shared_python, macos-14, python 3.12, Node 22
The real trigger might be running on single core CPUs and not macOS since older macOS hosts on GHA are single core.
None that I can think of.
The problem does not have a generic solution: https://stackoverflow.com/questions/37140799/passing-environment-variables-in-npm-scripts There are a number of npm packages that do this for plain npm actions.
I am trying to reduce the complexity of https://github.com/mmomtchev/magickwand.js/blob/meson/package.json Clean cross-platform method for setting the environment variables will help a lot. I am installing custom versions of `conan` and `meson`...
* `.cmd` is another problem. This comes from Node.js itself, which uses a spawn mechanism that requires the `.cmd`. I think that launching processes using a shell should resolve it?...
Alas, `shx` does not support setting environment variables - in fact, it has a very limited subset of the `bash` features. However `sh` from the Windows Build Tools seems to...
It is only now that I understood the `meson` package (I discovered the `meson.c` file), I will try to do the same with `conan`.
@ilg-ul, I have another use case for this: my static Python xPack now comes with root CA certificates - this was a problem mainly on macOS where it required that...
Second this, it is an important feature, since it will allow testing the release assets before publishing the release. In the mean time, you can use the `gh` CLI utility...