4 ms·
> as long as you place the libraries in the same folder as the executable The problem is that I don't know which libraries I need. For a very small project I j
by rgovostes 7y ago
> as long as you place the libraries in the same folder as the executable
The problem is that I don't know which libraries I need. For a very small project I just kept launching the .exe and reading error messages until I had gathered all the DLLs. It's not a sound way to do it, in case a library is loaded dynamically.
- longnguyen 7y agoFor Qt dlls, use windeployqt. For third-party libs you will still need to copy manually though
- geezerjay 7y ago> For Qt dlls, use windeployqt. This, and there are also applications which state which DLLs are missing from a deployment.
- maccard 7y agoHow would you have figured out which libraries you need if you were linking it statically? I'm not going to apologise for Windows DLL behaviour (side note, you can use `dumpbin /dependents` or `DependencyWalker` to track them down) as it's awful, but this is categorically nothing to do with QT.
- deleted 7y ago[deleted]