summaryrefslogtreecommitdiff
path: root/Settings.cmake
AgeCommit message (Collapse)Author
2023-07-19Remove macOS deployment target for now.John Fultz
This will hopefully fix the GitHub actions build. Definitely fixes my local build. This won’t stand for a deployment to users, but it works for developing.
2023-07-16Set the C++ standard to C++17.John Fultz
C++17 is a requirement for Qt6. It’s been out long enough that I think we’re safe just requiring it globally.
2019-08-06link threads in a properly crossplatform mannerMartin DeMello
2019-08-06add pthread to the cmake c++ flagsMartin DeMello
2019-07-19First cut of a cmake build.John Fultz
Building on macOS right now. cmake will soon replace qmake as the supported build system. Some notes about the implementation: * libquackle and libquackleio can be separately built as before. * quacker still links to the static libraries for libquackle and libquackleio, but quacker's cmake file includes those projects, which means everything builds at once. No more need to run separate builds of everything to get a GUI. And debugging is easier now that the libraries are incorporated into the quacker project. * I tried to get cmake to build the macOS app bundle, but cmake is unable, by conventional means, to build a non-flat Resources directory (which many people have complained about). Right now, the default build just builds the binary, and you have to run it from the command-line. But -DBUNDLE=ON will build a shell of a bundle. It won't work, but I intend to create an Xcode project from it for building the bundle, to make it easier for me to deliver a code-signed and notarized app bundle. * I've got CMakeLists.txt files for the resources, but they're not really doing anything right now. Maybe later. * Minimum macOS version for the cmake build is 10.10.