![]() ![]() ![]() Call Stack (most recent call first ) : D:/programs/qt/src/ 6. 1 /qtbase/cmake/QtProcessConfigureArgs.cmake: 223 ( message ) : ' -nomake tools ' is not implemented yet. 1" -skip qtwebengine -nomake tools -nomake tests -nomake examples CMake Warning at D : /programs/qt/src/ 6. 1 \qtbase\configure.bat -top-level -release -no-pch -prefix " d:/programs/qt/ 6. 1" -skip qtwebengine -nomake tools -nomake tests -nomake examples + cd qtbase 1 \build>.\configure.bat -release -no-pch -prefix " d:/programs/qt/ 6. 1 \build>cmake -version cmake version 3.18. There MSVC toolchain is detected just fine: I’ve set it here because otherwise by default with Ninja it discovers Clang toolchain, which I also have in my environment, but I want to build Qt with MSVC toolchain.Īnd while I could’ve tried to set cl.exe for CMAKE_C_COMPILER and CMAKE_CXX_COMPILER explicitly, I decided not to and just switched back to 圆4 Native Tools Command Prompt for VS 2019. Call Stack (most recent call first ) : qtbase/cmake/QtBuildInformation.cmake: 10 ( qt_configure_print_summary ) CMakeLists.txt: 87 ( qt_print_feature_summary )Īfter a brief googling I found that Visual Stugenerator is not supported. cmake : 72 ( message ) : Check the configuration messages for an error that has occurred. tests /atomicfptrĬMake Error at qtbase /cmake / QtBuildInformation. Please apply the patch corresponding to your Standard Library vendor, found in qtbase /config. ERROR: detected a std::atomic implementation that fails for function pointers. Open 圆4 Native Tools Command Prompt for VS 2019 and there:ĮRROR : C++ 11 is required and is missing or failed to compile. Let’s say you have downloaded/cloned sources to d:\programs\qt\src\5.15.2 and you would like to install Qt to d:\programs\qt\5.15.2. I’ll describe the process for Windows 10 and Visual Studio 2019 / MSVC 142 ( assuming that you have all that), but it will be almost the same with different toolchains and on other platforms too. Now when you have the sources, you can just build Qt and get the same binaries that are installed using installer. That will be actually much faster, and even though you can’t choose modules here, later you’ll be able to skip building unwanted modules with -skip option ( -skip qtwebengine, -skip qtactiveqt, -skip qt3d and so on). Or you can just get a source package ZIP archive from the download page. Be sure to check it in case you might actually need some modules which I excluded here. It took 40 minutes ( with my 3 MB/s connection) and 3 GB to initialize such a list. qtserialport ,-qtscxml ,-qtremoteobjects ,-qtqa qtquicktimeline ,-qtspeech ,-qtvirtualkeyboard ,-qtwayland ,-qtsensors ,-qtserialbus ,\ qtlottie ,-qtdatavis3d ,-qtgamepad ,-qtpurchasing ,-qtquick3d ,-qtquickcontrols ,\ init -repository -module -subset =essential ,addon ,-qtwebengine ,-qtactiveqt ,-qt3d ,\ Find the latest ( or whichever you need) release - it’s hard not to notice that branches match releases, so 5.15.2 branch is the latest release at the moment ( ). Getting the Qt sources Clone Git repository Failed pcre2_jit_compile.c.obj, oaidl.h.And certainly, you’ll still need to comply with GPL/LGPL terms ( depending on components that you’ll be using). ![]() Just to clarify and to TLDR the article: it’s not about pirating the binaries, it’s not about some hack or anything shady at all - everyone can get the Qt sources and build whatever version they want. But don’t even trip, dawg, as we’ll still be able to build LTS releases from sources without Qt Account and/or commercial license. In the very same blog post The Qt Company stated that LTS releases will be only available to commercial users, so The Qt Company can go fuck itself twice at this point. And now they fucking did it again, and apparently this time community wasn’t that mad ( or there is nothing left of that community after all the stunts The Qt Company has been pulling over the past years).Īnyway, I won’t tolerate such anal-probing, so The Qt Company ( or rather its management) can go fuck itself, and I’ll be just building Qt from sources - it’s not that scary as it sounds. That’s something that already happened before, but back then community got really mad about it, so The Qt Company reverted that, and installer started to work without Qt Account. More details in the Qt’s official blog post. At some point ( beginning of 2020 year) Qt installer started to require users to have Qt Account ( again), otherwise you can’t proceed with the installation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |