Errors using build[uv] in macos

[BishopWolf]

Description

Hello

I am trying to add homebrew cache before building my wheel

If I use

- name: Set up Homebrew
      if: (inputs.os == 'macos-15') || (inputs.os == 'macos-15-intel')
      id: set-up-homebrew
      uses: Homebrew/actions/setup-homebrew@main

Everything runs fine. However using

- name: Cache Homebrew prefix
      if: (inputs.os == 'macos-15') || (inputs.os == 'macos-15-intel')
      id: cache-homebrew
      uses: Homebrew/actions/cache-homebrew-prefix@main
      with:
        install: wget ccache fftw libomp xerces-c qt cmake
        uninstall: true
        workflow-key: ${homebrew-key}

I get errors in the CI. Basically the uv isolated environment loses the system python. Am I doomed to install qt everytime?

Build log

https://github.com/BishopWolf/opengate/actions/runs/23798872465/job/69353385037

CI config

https://github.com/BishopWolf/opengate/blob/windows-qt6/.github/workflows/actions_build/action.yml

EDIT

The exact same build that fails for python 3.11+ using cache, it strangely works for python 3.10
https://github.com/BishopWolf/opengate/actions/runs/23798872465/job/69353385033

[BishopWolf]

This is hardcoded (

cibuildwheel/cibuildwheel/platforms/macos.py

Line 128 in 643b30c

installation_path = Path(f"/Library/Frameworks/Python{ft}.framework/Versions/{version}")

)

Either the isolated uv environment does not have access to /Library/Frameworks OR python 3.11+ is not installed there . Which is odd since without the homebrew cache it is there. I don't know what else to think.

[henryiii]

We do need the official CPython that's compiled with a wide support window (and is always in that path, it's not relocatable), and not homebrew's Python. Is this done before the setup python step? I thought we installed CPython if it's missing (setup-python on Apple Silicon actually installs the official version starting at some point, maybe it was 3.11?, so we don't need to if you use it), but maybe something is confusing it that the homebrew step is setting up? (I agree, I'm confused that it would).

You should not be using things from homebrew to build wheels. Those are not compiled in a such a way as to be redistributable; this is expressly out of scope for the homebrew project. They don't support older macOS, for example. It's fine for things like cmake that are used but not put into the wheel, but it's not something you want to use for libraries that get bundled into the wheel.

[BishopWolf]

It seems that I need a new approach to get cached qt libraries then. However, the normal setup without cache + posterior brew install qt works fine for us. It just takes 10+minutes every build.

[henryiii]

Have you tried flipping the order of the cache and setup-python? Just in case that affects things.

[BishopWolf]

yep, both gave the same result. Its clear now that homebrew messes things up in the cache.

I just found jurplel/install-qt-action@v4 . Its working fine so far, and it installs fast enough 20 seconds instead of 10 minutes.
It will probably work for windows also.