spin: Additional windows problems
From the meson branch of NumPy, using the HEAD of this repo 2ad0423b8 in a virtualenv of the windows store CPython3.9 located in d:'\temp\cpython_39:
-
When starting from a cmd shell without cl on the path,
python dev.py buildfails to set up MSVC in a way that ninja can call it. I need to do this (something kindly prints out the second line so I know what to call, then the second invocation of dev.py installs tobuild-install). A work-around is to activate MSVC before calling this command, but I think it should Just Work without that.python dev.py build D:\temp\cpython_39\Scripts\meson compile -C build python dev.py build -
running
python dev.py teststill fails. It seems to be calling the base-python rather than the one inside the virtualenv. We touched on this in the other issue. If I change this line to usesys.executableinstead of"python"then it works.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 24 (24 by maintainers)
Baffling, because: https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md#msys2
Which makes a ton of sense! Every other gcc should do the same! Github Actions hosted tools should be available if the user wants to activate them, not arbitrarily sprinkled into PATH. But it failed at least twice and maybe more than that, sigh.
…
Hold on, msys2 isn’t the problem at all. LLVM 15.0.5 is installed too.
Clang is:
C:\Program Files\LLVM\bin\clang.exehttps://github.com/scientific-python/devpy/actions/runs/3915502106/jobs/6693736610#step:7:4
The functional tests try to build software using C, I don’t know why this is quitting in a single second while printing zero output though. Simply configuring Meson should take longer than that…