Open stevenwdv opened 9 months ago
I also noticed this some time ago, it looks like a bug to me.
And cross-compiling (at least Linux to Windows) with windeployqt is not supported (see here https://bugreports.qt.io/browse/QTBUG-77823?focusedCommentId=473297&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel )
Btw, similarly it also failed when compiling the tools as static, while I would expect that only the runtime would need to be shared.
Oh wait, it seems like crosscompiling qt is not actually supported yet... :/ See #20257 etc. https://github.com/conan-io/conan-center-index/blob/1c888e8686e4656c5046dd269045c713bd610d4e/recipes/qt/6.x.x/conanfile.py#L303-L304
What is your question?
Hello, I'm trying to compile and deploy a Qt6 application, and found some weird behavior. First, I install dependencies with a conanfile.py like the following:
(windeployqt doesn't work (or make sense, I guess?) with static libs.)
Then I build:
And then I try windeployqt:
And this works fine.
However, if I use something like this: (which was the first thing I tried)
I get errors from windeployqt (running with
--verbose 2
):So it seems that Qt was/is looking for DLLs in the build package folder instead of the host package folder. Is this intentional? This seems weird to me. Does this still work when cross compiling?
Btw, I think it obtains the Qt DLL folder path from
qtpaths.exe
in the build package folder, which contains absolute paths put in there when this executable is built.