I am on windows, but the company's policy and firewall restrictions make it very difficult to get and build the sources.

@tuzepoito said in How do I use Qt headers in a CMake sub-project?: I think I have a solution, or maybe a workaround. Why workaround? If you want to use a library, you have to link against it what you're doing now - how should this be a workaround?

My second solution would be much more portable.

Я так понимаю, под "поставить" подразумевается "собрать". Покажите полную команду для configure. Фотография экрана вместо скопированного текста консоли прошибла на слезу.

Do you mean how to add paths so that your .exe files can be run from Qt Creator, or adding paths so that your .exe files can be run without Qt Creator? In the first case (starting .exe files from Qt Creator) as long as you only have a single version of Qt installed on your PC, there should be no need to add any paths, as I said earlier, Qt Creator adds the path to the Qt dlls for you. In the second case (starting .exe files without Qt Creator) then there are 2 ways to do it: copy the Qt dlls to the same directory that your .exe file is in, either manually or by using the windeployqt.exe program adding the path to the Qt dlls to the PATH env. variable Note: LIBS += -LMyPath has no effect on runtime lookup of .dlls or .so files QMAKE_RPATHDIR has no effect on Windows, because Windows does not support adding a list of paths to your .exe/elf file where to find the Qt dlls/so files (works only on Linux and MacOS) Also on Linux, QMAKE_RPATHDIR is not needed for the first case (starting .exe/elf files from Qt Creator) since Qt Creator does that automatically for you (by issuing a linker command e.g. -Wl,-rpath,/home/user/Qt/5.15.2/gcc_64/lib)

Ok well here's an interesting discovery I've made, for anyone who finds this thread in the future: There seems to be an issue with the driver for the off-brand Arduino Nanos possibly not signalling to the OS correctly, or the implementation that Qt uses just really doesn't like the way that the driver responds. I am referring specifically to the nano clone which uses the QinHeng HL-340 serial peripheral. Not sure why this caused a problem, but there it is. Once I used an official Uno the code worked no problem. If I were more patient and had better resources I could possibly trace back the issue, but I do not, so sorry everyone lol. As such I'm marking this as resolved.

@Krakenus00 Hello can you add the picture that you want to achieve and one that you are getting

@sierdzio Thank you very much!

https://bugreports.qt.io/browse/QTBUG-87735 bug fixed) Fix Version/s: 6.0.0 RC

@Chris-Kawa Thanks, it works !

@mzimmers If i iterate over the interfaces like in your script, then it works with no problem :) Running on windows :) When using only the QHostAddress::Broadcast I get the wrong broadcast addr. I too think it is strange, but this is no issue for me, as it's always simple to determine the right address by code or manually :) just strange as you say :) Anways, off to new issues :D

I posted this Question on SO as well, who directed me towards a logger which made it really easy to see what was up and lead to an easy fix. Heres a link to the question if anyone would find it helpful: https://stackoverflow.com/questions/61035096/attempting-windows-deployment-exe-file-not-opening-with-no-error-messages/61036646#61036646

I see, thanks for the response. I stumbled today on an old thread where user wanted the same font rendering as in Photoshop. One of person responding said that they made their own wrapper of FreeType. I guess I will try to render icons using that and see where it goes. Not gonna mark it as solved for now though, maybe someone will stumble on it with some experience.

@bdfyy You can use this tool: https://github.com/JKSH/QtSdkRepoChooser

@JonB Not a big viewer at all. viewer is a simple QGraphicsView containing a QPixmapItem which is continually updated through another slot taking a signal from the camera thread every time it has a new frame, at 60fps. Part of the issue seems to be with the debug build, which is obviously a fair bit slower than release. In release it doesn't really seem noticeable, though I imagine it might be on a slow system. Still, I do find the asynchronous behaviour of raise() interesting. I tried looking a bit at the source code, but didn't really get anywhere. Because it's not a problem in release, I guess I'll just leave it be for now. Thanks for the help, though, much appreciated.

I reply to myself, just in case some else has the same issue. Switching the Jenkins build slave from Windows7 to Linux (Debian 10) has reduced the APK build time from 40 minutes to 8 minutes! Yes, my project is relative big ;) Regards Fabrice

@JDePedro Ok. I found the cause why I was not getting anything QML related from the tool. My widget is not in the exe file but in a DLL so I had to specify the dll instead. But the list of files the tool is getting is huge compared with the one I got by doing the process "manually" and includes most of the .qml files. So my doubt is, do we need to deploy all this files with my application? is not enough with the dlls???

@fcarney I can't beleive I missed your question. Comparing with Heob, Deleaker provides more features like taking snapshot at any moment, and comparing them later. Besides heap allocations, Deleaker also tracks COM/ActiveX/GDI/USER32 leaks etc.

Hi @ivec Is it normal that I needed to select the compiler manually? No. but please select the C compiler also. And how can I enable the use of a debugger to step through my program? You need to install the Debugging Tools for Windows, included in the Windows SDK. Due to licencing, this is not possible otherwise. Regards

@JonB Noooo... I did not understand that the enumeration of multiple paths in the Windows example referred to a list. Now I know :o) thanks.

@kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function: This address is rather suspicious. Please tell me you don't have global QWidgets? No, I have only a dll with function extern "C" CORE_SHARED_API QMainWindow * svCreateMainWindow() { return new MainWindow; } (CORE_SHARED_API is __declspec(dllexport)) @kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function: Btw, 0xc0000409 is stack overflow, so be on the lookout for endless recursion. As I said, QWindowsGuiEventDispatcher::processEvents() is called twice, and I believe those calls are on the same stack level (crush happens in the second call).

what is your suggestion about server app design ? People usually refer to "server app" as "middleware" or "web application". There are tons of web frameworks and ORMs for various languages including Java and C# on "enterprise" side and scripting languages (pphp, python, perl, ruby, node.js). C++ is not really convenient language here. As for protocol, if you are not pursuing real-time data processing with lowest possible latency, it makes sense to use REST API on top of HTTP, so that on server side you have the most typical "web app" with ORM inside and REST outside, and on client side you can easily add web client if needed, and even if not, you get some additional convenience as compared to e.g. RPC over plain TCP

Hi, An educated guess is that the second case is handled by the window manager (the decoration is not done by Qt). One possible thing to do would be to check the screen resolution in your method and try to adapt to that.

@smhrambo deleting the *.pro.user file often helps when you do such moves...

@SGaist Thank you inform about me QtSingleApplication class. I will modify code and use QtSingleApplication.

There is a way to force an external window to become part of a widget, but the API isn't really meant to be used this way and there are multiple issues: https://bugreports.qt.io/browse/QTBUG-45275

@wrekler ok. Im not sure what system buttons are. But yes, its most likely there are bugs as its pretty involving across platforms to support such decoration less window.