Note: Afaik, v5 on macOS does not have memory allocator changes compared to v4 (and isn’t even a rebuild), it simply changes the framework structure to work with Xcode 26.

Note: Afaik, v5 on macOS does not have memory allocator changes compared to v4 (and isn’t even a rebuild), it simply changes the framework structure to work with Xcode 26.

I can change the commit name if needed, I thought that v5 had malloc related changes.

The PR and commit description are correct now, though I wonder if I shouldn't just pull the ripcord and build an actual v5 with the allocator change included and the structural changes, as we are in no rush to bring this in to OBS 32 (the structural changes are just needed to have a working master branch once macOS 26 releases).

I've tried and it doesn't build with a fully disabled allocator shim, so it's probably good enough to keep v5 for its structural changes.

The PR and commit description are correct now, though I wonder if I shouldn't just pull the ripcord and build an actual v5 with the allocator change included and the structural changes, as we are in no rush to bring this in to OBS 32 (the structural changes are just needed to have a working master branch once macOS 26 releases).

For my part, I mostly want people to be able to build OBS Studio 32.0.x in Xcode 26 and on/for macOS 26.