>I'm a hater of complexity and build systems in general.
But you already have a complex cmake build system in place. Adding a standard Docker image with all the deps for devs to compile on would do nothing but make contributing easier, and would not affect your CI/CD/testing pipeline at all. I followed the readme and spent half an hour trying to get this to build for MacOS before giving up.
If building your project for all supported environments requires anything more than a single one-line command, you're doing it wrong.
>> But you already have a complex cmake build system in place.
I didn't build it :-(
>> Adding a standard Docker image with all the deps for devs to compile on would do nothing but make contributing easier, and would not affect your CI/CD/testing pipeline at all.
I understand, but to me that's just more stuff to maintain and learn. Everyone wants to push their build setup upstream - snap packages, flatpak, now we need docker... And then you and I complain that the build system is complex, partly because it supports so many options. But it looks like the person taking up the AI challenge here is using Docker, so maybe we'll get that as a side effect :-)
I'm sympathetic in general, but in this case:
"You will need git, XCode tools, CMake and libomp. Git, CMake and libomp can be installed via Homebrew"
That really doesn't seem like much. Was there more to it than this?
Edit: I tried it myself and the cmake configure failed until I ran `brew link --force libomp`, after which it could start to build, but then failed again at:
[ 55%] Building CXX object src/CMakeFiles/solvespace-core.dir/bsp.cpp.o
c++: error: unknown argument: '-Xclang -fopenmp'