[08:48] <lubot> <mitya57> Hi @Zurd0s! I haven't heard anything about this issue. I will suggest you to use strace to find which directories Qt searches for plugins in.
[08:51] <lubot> <mitya57> @Zurd0s [I think I've disabled the relocation thing (-no-feature-relocation...?) but beha …], Features are listed in qconfig.h, if I remember correctly.
[08:51] <lubot> <mitya57> Also maybe you will get more lack if you ask on #qt-labs.
[13:08] <lubot> <Zurd0s> @mitya57 [Hi @Zurd0s! I haven't heard anything about this issue. I will suggest you to use …], I ended up doing so. Using quassel as an example, it was only looking in its own package for plugins (on NixOS packages don't share hierarchy: quassel has its own /lib, isolated from qt's. And, in fact, qt produces at least two different
[13:08] <lubot> /lib directories, but that's another story...). However, I believe we managed to fix this by forward-porting a patch that we used in 5.12 (probably before too) that didn't apply on 5.14 (situation on which we defaulted to dropping the patch, of course). It appears most of the weirdness left on update is related to QML module paths now, but now we h
[13:08] <lubot> ave a method :P
[13:09] <lubot> <Zurd0s> @mitya57 [Features are listed in qconfig.h, if I remember correctly.], There's not a single qconfig.h on my system that has anything resembling "relocatable", so it's either not it, or I didn't disable it correctly. Still, thanks!
[13:09] <lubot> <Zurd0s> @mitya57 [Also maybe you will get more luck if you ask on #qt-labs.], I'll try. Thank you!