@JoeCFD Hello , thank you for this answer .. building this is not easy for me on windows. could'nt find a complete tutorial without using docker images or msys2 App. Meanwhile i tried to run the QtPlayer example in "doc\libvlc\QtPlayer" . It runs without error when i changed my .pro ... but video does'nt start affter selecting the file. What am i doing wrong ?

I managed to solve it by moving an #include (of the class that has the #include "ExpressionEvaluator/exprtk.hpp" in it) that was in a .cpp file to the .h file and putting it before the #include of the class that has the #include <windows.h> in it. Thanks everyone for the help.

@Kim-Nancy said in Problem compiling for Android from Windows: Seek assistance on Qt community forums for further support. Ha, that's literally where we are. In any case, this solved it for me: https://stackoverflow.com/a/68394638/8548472.

@UvQtcYZJuD7J5VW7 said in Dependencies missing after DLL compilation: Unfortunately, LabView is not very talkative. This is the only error message I get. I have already recreated the node. Ah, check the dependencies of the DLLs that you deployed. For example, libgcc_s_dw2-1.dll depends on other DLLs too. Otherwise I could programming the entire program in Qt and so I will not have the need to use a DLL. If you can do everything in 1 language, that makes life a lot easier.

@zeethree50 said in Libicu, needed by Qt5Core, compilation issues. Please help!! Worked fine in 18.04, but not 16.04.: And it worked for me Great, so please don't forget to mark your post as solved!

@Eager, it worked for me. Thanks!

@koahnig Thanks so much

I also encountered this problem. It can be solved by manually adding the following definition of this structure (from Raspberry Pi Video Core API) into EGL/eglplatform.h (adding additional definition will not break compilation on non-legacy code that does not use this structure). And you also need to add the definition of DISPMANX_ELEMENT_HANDLE_T before that. i.e., typedef uint32_t DISPMANX_ELEMENT_HANDLE_T; typedef struct { DISPMANX_ELEMENT_HANDLE_T element; int width; /* This is necessary because dispmanx elements are not queriable. */ int height; } EGL_DISPMANX_WINDOW_T; After doing this, you will still encounter a few compilation errors in pointer casting. You can just forcefully cast all pointers over (or copy my code ). The compilation should proceed then. The reason why the compilation breaks is because in the open-source community, many developers still come from private companies working on proprietary projects. Some need to show to their boss that they have done something, so they unnecessarily keeps changing definitions, names, removing structures they do not know about due to their ignorance on other platforms/architectures (so they can say "oh, I did code-base clean-up"). In the end, it causes massive compilation breaks/failures. However, the underlying code is still the same, that is why directly casting pointers over surprisingly works out in the end, which should not be the case if substantial development is present. In summary, the No.1 development principle is that code modification should be made as minimal as possible and should exist if and only if necessary.

Hi and welcome to devnet, That's a question you should rather bring to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

Hi and welcome to devnet, Qt Creator should auto detect the compiler for you. However what usually happens is that people install Visual Studio without checking the C++ option during installation thus they have a VS environment but nothing to build C++ code. You should first check that. Note that you also need to install the debugger separately. The one coming with VS is "internal" and cannot be used by other applications.

I did install the one coming with the Qt package, there is no other version installed.

@koahnig said: Either you need to add "-j4" as make parameter to each of your projects. Otherwise you can set also "MAKEFLAGS=-j4" to your environment (e.g. for a kit as suggested above). Correction to above post. I have set it to system environment. I did not get it to work in kit environment. Both were set due to my trials, but the latter alone (in kit environment) does not help.

That's a good news but still a strange mystery… By the way, no need to modify the thread title, you can mark it as solved using the "Topic Tool" button :)

That one's a classic (and a question that regularly comes back)

Fine, Thanks.

@jitu059_Lalat The long and short if it are, you have two ways to do this: Find all the dll's that your app depends on. You can do this with the tool http://www.dependencywalker.com/. Once you found all the dll's copy them into the same folder as your executable. This is now your "delivery package" you will copy the executable + dlls from PC to PC. This method is perhaps a bit easier/faster in the short term, but when you compile with different versions of Qt/Windows you may require a different set of dlls (i.e. Qt4 Dlls don't match Qt5 Dlls). Download the Qt source code and compile it for static linking. Then when you build your code you will get a much larger executable file, but it will contain everything it needs - a standalone executable. This is perhaps a bit more work on your part, but master this and it makes deploying your project from PC to PC much easier. Have a go at one or other method, if you get stuck then ask again. But as SGaist said, there is lots of documentation out there already : )

You did a complete rebuild as well? The run of qmake does not create an error code, but it does not introduce a moc statement into makefile. I guess you are using a shadow for compiling. Delete the whole shadow folder, rerun qmake once again and rebuild. If you think it imay be a bug related to Qt 5.5 you can check on JIRA.