Thanks a lot for confirming!
Just to clarify a bit further (not easy, English is not my native language):
Even though I’m linking the individual frameworks (sfml-graphics.framework, sfml-window.framework, etc.), I still rely on the presence of SFML.framework, even if it’s only built for x86_64 (without it, it would not compile).
Surprisingly, building for arm64 actually works as long as I include the x86_64 SFML.framework alongside the others (in arm64). It’s a bit strange (I guess macOS or the linker just silently accepts it) but it feels more like a lucky accident than a robust solution.
Maybe SFML.framework only contains headers and metadata, which would explain why it technically works even if it was built for x86_64 only, the compiler probably just uses it as a header bundle (I do not know, just a guess).
That’s why having a proper SFML.framework for the arm64 architecture would make things much cleaner and more reliable, especially when maintaining cross-architecture builds.
Anyway, glad to hear it’s likely to be fixed in 3.0.1!
wEconomiKus