cmake-init VS cmake-sfml-project

It's easier to list what is not wrong about CMake. The only positive thing about CMake is that it works once you spend days or weeks ripping your hair out trying to configure it. cmake-init is a perfect example of what is wrong with it. Over 400 commits, lots of files to properly start a project. No other language does that, because it is unspeakably bad.

Okay, so I'm assuming /Users/kadyr is the username for your mac, so let's say you are making an SFML Space Invaders clone. You'd make a directory invaders so it would be /Users/kadyr/invaders then make a CMakeLists.txt file in invaders and copy the contents of the template's [CMakeLists.txt](https://github.com/SFML/cmake-sfml-project/blob/master/CMakeLists.txt) into it. Next, in invaders directory create a build directory [/Users/kadyr/invaders/build] and a src director [/Users/kadyr/invaders/src] to put main.cpp and other code in (this one is just because the template looks for main.cpp in /src -- alternatively you could edit the add_executable() line and remove src/ if you plan to just dump all code into invaders directory). Then run the commands. Just change invaders to whatever you are naming the project and directory you're working on.

Source

Why didn't you just use brew to install SFML? What about building SFML 2.6.x instead of 2.5.1 which already has ARM Mac fixes you described? Have you already tried the official CMake project template which automates much for this for you?