Details
-
Bug
-
Resolution: Invalid
-
P1: Critical
-
None
-
6.1.0 Alpha
-
None
Description
$ cd ~/dev/qt6-dbg $ ../qt6/configure -developer-build -nomake examples -ccache ... ... Qt is now configured for building. Just run 'cmake --build . --parallel' Once everything is built, Qt is installed. You should NOT run 'cmake --install .' Note that this build cannot be deployed to other machines or devices. To configure and build other Qt modules, you can use the following convenience script: /Users/rutledge/dev/qt6-dbg/qtbase/bin/qt-configure-module If reconfiguration fails for some reason, try to remove 'CMakeCache.txt' from the build directory -- Configuring incomplete, errors occurred! See also "/Users/rutledge/dev/qt6-dbg/CMakeFiles/CMakeOutput.log". See also "/Users/rutledge/dev/qt6-dbg/CMakeFiles/CMakeError.log". CMake Error at /Users/rutledge/dev/qt6/qtbase/cmake/QtProcessConfigureArgs.cmake:797 (message): CMake exited with code 1. $ xcodebuild -version Xcode 12.3 Build version 12C33
Yes it's an empty build directory and the source dirs are clean. Yes I've tried using cmake directly instead of configure. Yes I've tried various arguments. Yes I upgraded XCode to 12.3. Yes I even upgraded to Big Sur. It hasn't affected this, haven't been able to build for a couple of weeks now. However on an older machine that has code from Jan 8 or so, it still builds.
I'm really tired of the fact that it says it configured correctly and is ready to build, and then says at the end that there were errors.
It's also not that clear from the error log which errors are from testing for various things that aren't there on this platform, and which one actually is the reason that no ninja file was generated.
How about the ones that say stuff like
src.cxx:9:22: error: 'path' is unavailable: introduced in macOS 10.15
That makes no sense given that I have Big Sur now right?