Installation and Deployment

@Grit-Clef I mean to check the access rights for the DLLs where you get "could not be found" ("but those dlls are there...").

/usr/bin/c++ is the local compiler on Linux, not the cross-compiler, which on my system is x86_64-w64-mingw32-g++. That means, something in the configure step went wrong or the toolchain hasn't been installed correctly. See here for more info: https://doc.qt.io/qtvstools/qtvstools-how-to-cross-compile.html

So it won't copy the pdb files from my build dir to the deploy dir - OK understood - though I think it should!

Hi, How are you doing the notarization ?

@ZergedU said in Cannot run Qt Online Installer on Red Hat UBI 9, libxkbcommon-x11.so.0 missing: It looks like Red Hat UBI 9 strips down the AppStream repo from the RHEL version. Notably, the package "libxkbcommon-x11" is missing. Ah... that's a shame. I guess you'll need to resort to a 3rd-party repo then? (Or build it from source)

Hi @nazim, and welcome! The service provider was down for several hours: https://www.bleepingcomputer.com/news/technology/massive-heroku-outage-impacts-web-platforms-worldwide/ It is back online now, and you should be able to log in again.

Hi @montanaviking, open your downloaded file with a text editor. You'll see that curl has saved a HTML document, not an executable. Either use a web browser to download it, or ask curl to follow redirects.

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.