Installation and Deployment

Ah, ok, thx.

I tried this: if(NOT LINUX) set (deploy_tool_options_arg "-verbose=1") if(APPLE) set(deploy_tool_options_arg "${deploy_tool_options_arg} -hardened-runtime -timestamp -no-strip") set(deploy_tool_options_arg "${deploy_tool_options_arg} \"-executable=$<TARGET_BUNDLE_CONTENT_DIR:DeepSkyStacker>/MacOS/DeepSkyStackerCL\"") set(deploy_tool_options_arg "${deploy_tool_options_arg} \"-executable=$<TARGET_BUNDLE_CONTENT_DIR:DeepSkyStacker>/MacOS/uchmviewer\"") set(deploy_tool_options_arg "${deploy_tool_options_arg} \"-codesign=Developer ID Application: David Partridge (VH8AYT3C7Y)\"") and it seems to have worked ... Was that the best way to do it?

Same problem here with Qt 6.9.1: libunwind.dll and libc++.dll are missing. I believe it worked previously with Qt 6.8.0. And again, copying those files from C:\Qt\6.9.1\llvm-mingw_64\bin fixes it. Is it broken again or did I make a mistake?

@M4Z4 Hi, I'm not 100% sure I follow your launching process, but the error you're getting looks a lot like you are not setting the wayland display export in the same terminal as you run the QT application. Specifically, this part of the error message: Jan 13 11:55:32 sm2s-imx8mp cpx.sh[1628]: qt.core.plugin.factoryloader: Got keys from plugin meta data QList("wayland-egl") Jan 13 11:55:32 sm2s-imx8mp cpx.sh[1628]: qt.core.plugin.factoryloader: checking directory path "/opt/cpx/platforms" ... Jan 13 11:55:32 sm2s-imx8mp cpx.sh[1628]: qt.core.library: "/usr/lib/plugins/platforms/libqwayland-egl.so" loaded library Jan 13 11:55:32 sm2s-imx8mp cpx.sh[1628]: Failed to create wl_display (Connection refused) Jan 13 11:55:32 sm2s-imx8mp cpx.sh[1628]: EGL: Warning: No default display support on wayland Jan 13 11:55:32 sm2s-imx8mp cpx.sh[1628]: qt.qpa.wayland: EGL not available Jan 13 11:55:32 sm2s-imx8mp cpx.sh[1628]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland-egl" in "" even though it was found. The connection to the display screen is refused. It looks like either 1) Your path to the wayland display is wrong (check ls -l ${XDG_RUNTIME_DIR}/${WAYLAND_DISPLAY} before running your QT application) or 2) the user running QT does not have permissions. You should be able to see test applications like weston-flower work as well

I reinstalled qt creator, and then i could compile (this also upgraded version from 6.9.0 to 6.9.1). Dont know what happend. I found one more clue. If i made a cmake project and targeted c++11 i could compile, all other combinations of cmake/qmake c++11/14/17 did not work.

It's explained here.

Use a recent installer version.

you were close, the right way to exclude this lib would have been -exclude-libs=libqsqlmysql

I hit the same problem when compiling hpp_proto after configuring and generating CS2022 solution. I got fatal error LNK1104: cannot open file '..\vcpkg\installed\x64-windows\debug\lib.obj' the generator had added "..\vcpkg\installed\x64-windows\debug\lib" instead of "..\vcpkg\installed\x64-windows\debug\zlibd.lib" under %AdditionalDependencies% Fixing that solved my issue.

@User-Name Found the solution , go to this URL: https://download.qt.io/static/mirrorlist/ and copy link ( HTTP) and launch your installer with your installer location --mirror [URL copied ] example for india : & '.\qt-online-installer-windows-x64-4.9.0.exe' --mirror https://mirror.ossplanet.net/qtproject/

In that case I would likely provide each as an installable option and have the cli provided through both of them. Of you can also create an installer that will setup all three of them independently.

@Tom_B said in No Qt platform plugin could be initialized: Thank you very much for your comment. I set both varibles to 1 in both sections, User variables and System variables, restated the PC. However, the qt installator threw the same error code and did not start. QT_WIN_DEBUG_CONSOLE expects a value of new or attach. 1 is probably the same as not setting it.

idk, i did that on the same configuration as before, and it worked :/ I did not understood why it did not worked (reason why i made this post) Now i don't understand what i did to make it work

Qt5 was the only solution indeed, but I needed to install some recent library, some that i had missintepreted for Qt6 library. I inherited a mess of several Go of source code on which several peoples during more than 12 year have put their finger without leaving any documentation. And the Qt installer did not help much, sins the base one doesn't allow to have Qt5, you need to have a mirror version to access archives, (i was trying to install Qt5 sins the first post of @jsulm ) To end the topic, if anyone have the same issue as me : Need to use QtScript but only have the most recent Qt and no way to install Qt5 : this post helped me too https://forum.qt.io/topic/160611/installing-qt5-on-the-latest-online-installer/3 (where i just noticed that is was jsulm who gave the answer )

Sorry not to reply sooner, I have been away. The project was created by VS over a period of time. THere is no CMake files as said. I guess it's some weird VS bug.

@Andy314 Marked it as solved for you ;) It was set as a "normal topic", which disables the Solved/Unsolved feature. :)

But that's an openSUSE problem that they renamed the packages from qt-<foo>-devel to something else :)

okay got it guys. thanks!

Can you explain the link between Qt and accessing low level stuff like the sensors ?