Installation and Deployment

You must import the plugin with Q_IMPORT_PLUGIN(QMYSQLDriverPlugin)

There might be several options: Use udev to trigger a helper script that will mount the usb drive when plugged, check the content of the drive and apply the update. Have an update mode in your main application that will trigger the update. Does the update require a reboot of the system ?

Hi, Did you check the date/times of your files ? Do you have your clock that is off ?

@SGaist said in [SOLVED] How to create symlink for libs? Debian Wheezy.: sudo apt-get install mesa-common-dev This still works. Just loaded a fresh Mint Linux, then needed to run sudo apt update sudo apt install build-essential sudo apt-get install mesa-common-dev to get it to compile. Thanks

@jsulm So, after statically building Qt, I have to build these 65 libraries: libxcb-glx.so libxcb-icccm.so libxcb-image.so libxcb-shm.so libxcb-keysyms.so libxcb-randr.so libxcb-render-util.so libxcb-render.so libxcb-shape.so libxcb-sync.so libxcb-xfixes.so libxcb-xinerama.so libxcb-xkb.so libxcb-xinput.so libSM.so libICE.so libxkbcommon-x11.so libjpeg.so libtiff.so libgbm.so libdrm.so libudev.so libX11-xcb.so libxcb.so libwayland-egl.so libEGL.so libXcomposite.so libX11.so libfontconfig.so libfreetype.so libdbus-1.so libwayland-cursor.so libwayland-client.so libxkbcommon.so libpng16.so libharfbuzz.so libz.so libdouble-conversion.so libicui18n.so libicuuc.so libdl.so libglib-2.0.so.0 libGL.so libm.so libgcc_s.so libxcb-util.so libuuid.so libbsd.so liblzma.so libjbig.so libwayland-server.so libexpat.so librt.so libXau.so libXdmcp.so libGLdispatch.so libsystemd.so libffi.so libgraphite2.so libicudata.so libpcre.so libGLX.so liblz4.so libgcrypt.so libgpg-error.so and only then will I get a statically-builded hello-world? Why isn't this mentioned in any manual? p.s. I know about exclusion libraries: linux-vdso.so libc.so libpthread.so ld-linux-x86-64.so They cannot be assembled statically. But what about the rest?

@SGaist Right! Figured that out, thank you. Now trying to figure out why the "make install" appears to be rebuilding everything when I typed it right after the make succeeded (I posted a separate query).

I have resolved the problem. When you disable threading it disables http as a consequence. See src/network/configure.json

@SGaist Thanks, :)

Hi, It looks like you are trying to re-create the Qt Installer Framework. It might already provide everything you need.

I came across the same issue and noticed that the reason was the line "set trace-commands on" in my "~/.gdbinit" file. This seems to modify the output of gdb such that parsing the python version number fails. Therefore I suggest: *) Qt creator users should make sure that the "trace-commands" feature in gdb is disabled. *) Qt creator developers should explicitly switch off the "trace-commands" feature after establishing the connection with gdb or modify the parser such that it can deal with the additional trace output. Hope that helps (at least it does for me), Markus

AFAIK, no it's not exclusive to Windows however that's one of the main platform that needs that for CI as Linux distributions all have Qt development packages. However that does not stops you from using it on Linux as well.

@hskoglund No [image: 1c7d472f-e3bc-4bfb-b0d6-b77cfa3aa00a.png]

Hello guys I had similiar issue and I got some solution. In my case I was trying to make a crosscompilation between my VM with ubuntu 20 and RPI with ubuntu server 20. I was using this guide https://github.com/abhiTronix/raspberry-pi-cross-compilers/blob/master/QT_build_instructions.md For some weird reason when there is line in qmake: QT -= gui it removes -L/home/jakub/rpi-qt/sysroot/usr/lib/arm-linux-gnueabihf from command line while building. So I added to qmake: LIBS += -L/home/jakub/rpi-qt/sysroot/usr/lib/arm-linux-gnueabihf Now it works fine. So try using line in *.pro file but change your <path to sysroot>. LIBS += -L<Path_to_sysroot>/sysroot/usr/lib/arm-linux-gnueabihf

Thanks @Christian-Ehrlicher I solved the problem by adding the project folder to the directory where I installed qt, it's not the most comfortable but it's what worked for me