Installation and Deployment

@jsulm Thankyou very much for said support. Everyone is learning and discussing over the world parallelely. Thanks a lot.

Hi, Thanks for all support. Finally, cross-compilation of beaglebone with Qt done. But, still , next stone in the path is - https://forum.qt.io/topic/124754/remote-generic-linux-device Please guide, what statement to add install in Cmakelists.txt file

tried with qt 5.9.1 static with msvc 2017 on window 10 failed. tried with qt 5.15.4 static with msvc 2017 on window 10 failed. tried with qt 5.14.2 static with msvc 2017 on window 10 is successful.

Hi, That's a question you should bring to the Qt Company since it's a commercial release.

@yanni You can forward the stdout/stderr output into a file and search there for "error". You can also call make again - it will not rebuild what was already built, so it should be easier to spot the actual error.

Hi and welcome to devnet, This thread and some others on this forum are about the same subject. You may find there some information to get you going.

Hi, For me, executing C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build>vcvars32.bat x86 from cmd was giving the below output: The system cannot find the path specified. ** Visual Studio 2019 Developer Command Prompt v16.4.5 ** Copyright (c) 2019 Microsoft Corporation The system cannot find the path specified. The system cannot find the path specified. [vcvarsall.bat] Environment initialized for: 'x64' This solved it: https://stackoverflow.com/questions/64248886/visual-studio-c-build-tools-vsdevcmd-bat-vcvarsall-bat-fails-to-find-some Best, Alex

So the advice I got from Qt support was: "Qt 5.15.10 should be available through the maintenance tool but it is required to remove the old open source installation completely and also remove the open source license files from your system. So, first step is to remove the old Qt installation completely. Then remove the old open source licenses which might exist." I am surprised they didn't make that clear when I upgraded or when I ran the MaintenanceTool (presumably it can detect the new license from my online account).

@jsulm Oh, thank you for the reply. I ask for qt company about this question too. I think they can give me a solution. Thank you again! Best Regards, JESuh

@AddieRae said in How to download 5.15.1?: There is, but like I said, it only goes up to 4.14. It doesn't have 5.15 on there to download. Use the online installer: [image: y4mqhPzLmRPn4gLWwNONw-xByJ621GqCj3L2LfuDgB8KnRSgMyB12Li26bRdlG5XBJDUIFeDa67NOszfwkslMjzNynx6IRVGeVz1jP9RiIqKhImWk7NSWjNW2rRkVcYJ1Ev9hdcJtQ6dbxnUaFVDT7E0Yeh5nFVztoSnTGzz_x0QLvjKqVbXeAjvceOIqcRY1jG?width=952&height=638&cropmode=none] My college instructor wants us to use 5.15.1 That's a strange request. May I ask why? it doesn't behave the same and won't allow me to do the work I need to. What doesn't behave the same? Qt 5.15.2 is backward compatible with Qt 5.15.1.

@Christian-Ehrlicher Your link no longer works - but given as it has Mingw8 in the name, I'm assuming that you were referring to a Qt 5 build with MinGW 8. While officially Qt 5 is dead now and no longer actively supported for open-source, I also ran into the issue @gyorokpeter was having. Specifically, I am using MinGW 11.2 (the bundled MinGW compiler for Qt 6) to compile the latest Qt 5 LTS. So to conclude, yes, Qt compiles fine with MinGW, but Qt 5 breaks when using a newer MinGW compiler. It passes the d3d12 config.test in qt/qtdeclarative, but then fails to compile the rest of the d3d12 plugin. This is what I had to do to make Qt 5 compile again under MinGW 11.2: diff --git a/src/plugins/scenegraph/d3d12/qsgd3d12engine.cpp b/src/plugins/scenegraph/d3d12/qsgd3d12engine.cpp index 75bde2c66b..3594878eca 100644 --- a/src/plugins/scenegraph/d3d12/qsgd3d12engine.cpp +++ b/src/plugins/scenegraph/d3d12/qsgd3d12engine.cpp @@ -221,7 +221,7 @@ static void getHardwareAdapter(IDXGIFactory1 *factory, IDXGIAdapter1 **outAdapte if (SUCCEEDED(factory->EnumAdapters1(adapterIndex, &adapter))) { adapter->GetDesc1(&desc); const QString name = QString::fromUtf16((char16_t *) desc.Description); - HRESULT hr = D3D12CreateDevice(adapter.Get(), fl, _uuidof(ID3D12Device), nullptr); + HRESULT hr = D3D12CreateDevice(adapter.Get(), fl, __uuidof(ID3D12Device), nullptr); if (SUCCEEDED(hr)) { qCDebug(QSG_LOG_INFO_GENERAL, "Using requested adapter '%s'", qPrintable(name)); *outAdapter = adapter.Detach(); @@ -238,7 +238,7 @@ static void getHardwareAdapter(IDXGIFactory1 *factory, IDXGIAdapter1 **outAdapte if (desc.Flags & DXGI_ADAPTER_FLAG_SOFTWARE) continue; - if (SUCCEEDED(D3D12CreateDevice(adapter.Get(), fl, _uuidof(ID3D12Device), nullptr))) { + if (SUCCEEDED(D3D12CreateDevice(adapter.Get(), fl, __uuidof(ID3D12Device), nullptr))) { const QString name = QString::fromUtf16((char16_t *) desc.Description); qCDebug(QSG_LOG_INFO_GENERAL, "Using adapter '%s'", qPrintable(name)); break; diff --git a/src/plugins/scenegraph/d3d12/qsgd3d12engine_p_p.h b/src/plugins/scenegraph/d3d12/qsgd3d12engine_p_p.h index a95cbb1cbb..54a2c4dc8f 100644 --- a/src/plugins/scenegraph/d3d12/qsgd3d12engine_p_p.h +++ b/src/plugins/scenegraph/d3d12/qsgd3d12engine_p_p.h @@ -55,6 +55,7 @@ #include <QCache> #include <d3d12.h> +#include <d3d12sdklayers.h> #include <dxgi1_4.h> #include <dcomp.h> #include <wrl/client.h> @@ -263,8 +264,8 @@ private: void beginFrameDraw(); void endDrawCalls(bool lastInFrame = false); - static const int MAX_SWAP_CHAIN_BUFFER_COUNT = 4; - static const int MAX_FRAME_IN_FLIGHT_COUNT = 4; + static inline const int MAX_SWAP_CHAIN_BUFFER_COUNT = 4; + static inline const int MAX_FRAME_IN_FLIGHT_COUNT = 4; bool initialized = false; bool inFrame = false;

Hi and welcome to devnet, Can you share your CMakeLists.txt file ?

It seems to be a bug, see here and here To solve this, the configure comamnd should be adjusted: ./configure --iconv=posix The syntax is a little bit different from that in configure --help output, see here

Then please mark this topic as solved, thx.

Hi, @TheNoodleNator said in import problem under PyCharm uic is not found: @SGaist Hi, if it wasnt meant to be imported. Why is there documentation found here that shows us how to import it? I learned something new, thanks ! It's something that is specific to PyQt5 and quite frankly I have never came across it until now. From a quick look, it does not seem to be documented as public API to be used by Qt applications. The main things I found boils down to: python3 -m PyQt5.uic.pyuic mywidget.ui -o mywidget.py The standard way to use .ui files is through the QtDesigner module either by using pyuic5 to generate a python file from your .ui file or use of the QUiLoader class. See here for a more detailed explanation.

@Henning-G Henning, you are a genius! That worked. I tried it on my Kubuntu 22.04. I used this method: wget https://launchpad.net/ubuntu/+source/gdb/12.1-0ubuntu1/+build/23606376/+files/gdb_12.1-0ubuntu1_amd64.deb sudo apt install ./gdb_12.1-0ubuntu1_amd64.deb So, it looks like gdb --version says 12.1 now and debugging works now.

@LoveAndMercy If you sue CMake then you should be able to work on your Qt application in Visual Studio Code by simply opening the CMakeLists.txt file. https://www.kdab.com/using-visual-studio-code-for-writing-qt-applications/

/path/to/Qt/MaintenanceTool -d starts it with verbose output to std::out /path/to/Qt/MaintenanceTool -help shows all other command line options