Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
The only cache files CMake generates are in the specified build directory, so if you've wiped that out and/or built from a clean checkout, cache files from an old build cannot be the issue (by the ...
#1: Initial revision
by
InfiniteDissentâ€
·
2025-09-26T12:34:40Z (12 months ago)
The only cache files CMake generates are in the specified `build` directory, so if you've wiped that out and/or built from a clean checkout, cache files from an old build cannot be the issue (by the way, you don't need three lines to initialise the build directory: a simple `cmake -S . -B build` in the source directory will do it in one step). A quick grep of the source code does not indicate any obviously hard-coded SDK versions or paths (which are possible in CMake, using e.g. the [CMAKE_OSX_SYSROOT](https://cmake.org/cmake/help/latest/variable/CMAKE_OSX_SYSROOT.html) variable), so my guess is that the SDK requirement is coming from a dependency. The INSTALL file mentions that Qt is a required build dependency, and the CMake script is using `find_package(Qt ...)` to locate it, without using any local path overrides. Therefore I would assume that you need a system-wide installation of Qt in order to build this software. Is it possible that the particular version of Qt you have installed on your Mac needs to be upgraded to a later point release in order to support the latest XCode and its SDK?