Andrei Yankovich
Andrei Yankovich
I found a bug in the code. it's not work for you because your qt located in specify folder x86_64-w64-mingw32 but at now cqtdeployer supports only ``` "x86_64-linux-gnu"; "aarch64-linux-gnu"; "x86_32-linux-gnu";...
About the **qmake6 -query** it's not work for snap applications. So cqtdeployer try to initialize qt by default templates.
> Hm, I don't understand? I'm not using snap applications? No, it looks as bug, I will fix it. But for now you can try to use deb (if it's...
@higaski I take this issue to work, but still not understand why the started QProcess of qmake6 returns empty result string of the qt configuration ``` Warning: Wrong output from...
> It should be the same environment. I'm invoking CQtDeployer through a custom CMake command. I can also reproduce the issue by simply launching CQtDeployer from my shell. > >...
> Hm, very strange. I've just built CQtDeployer from source and passed the same arguments and that worked (invoking the CQtDeployer executable directly, not through the script). > > Looks...
> You're correct yes, the version I've compiled myself works with the launch script as well. God this is confusing... 😆 It is fine for classes as QProcess. Therefore, I...
@higaski i closed this issue and moved qtconf option to separately task.,
i was checked your example, and found some issues with project structure, that cannot, allow deploying your plugin, and i found issue that i need to make a simple research...
i close this issue, because it is inactive