meson-python link.exe issue since 3.3.0 release

[jeandet]

Description

I tried to update my CI scripts to use the latest (3.3.0) cibuildwheel release, but somehow it seems to mess with the way meson finds msvc link.exe. I tried several cibuildwheel versions:

• 3.3.0 ❌
• 3.2.1 ✅
• 3.1.1 ✅
• 2.23.3 ✅

I tried look quickly in the release diff between 3.3.0 and 3.2.1 I didn't see anything obvious.
I believe I also have the correct Meson setup.

Build log

https://github.com/SciQLop/SciQLopPlots/actions/runs/19391928744/job/55486608055

CI config

No response

[henryiii]

v3.2.1...v3.3.0

I see #2630; That's now modifying the path, rather than just pointing at cibuildwheel. If there was anything else in that location, that would get exposed too. However, it seems to be pretty carefully exposing only the binaries. I don't think that change is actually needed, since we use uv.find_uv_bin() to find uv if it's installed alongside us, but I don't see how that would have broken anything.

The windows.py file didn't really change in a way that could affect this.

Build dep pinning changes shouldn't affect meson-python.

Other than that, just normal dependency updates, which I wouldn't think would affect a Windows build. I'd be curious to see a build from just before / just after #2630.

[henryiii]

Better yet, could you try #2673 on your workflow? Just use @henryiii/fix/simpleraction instead of @3.2.1.

[jeandet]

@henryiii thanks a lot for your help, I started a build here, it seems to work so far.

[Starbuck5]

@henryiii I ran into the same problem as jeandet on my project.

Using your custom branch fixes the problem. Tested here: pygame-community/pygame-ce#3655