Eek, yeah, I didn't have a global Qt install when I was testing. I do bundle the Qt libs along side. Maybe change LD_LIBRARY_PATH to local dir? I have filed an issue: https://github.com/cretz/doogie/issues/45. That's why it's an alpha release :-)
Perhaps you can fix by calling dlopen on the shared objects explicitly rather than linking them and relying on the linker to find the libraries at runtime. I'm not sure, not totally familiar with C linking.
You should look into distributing an AppImage. Its author has a very nice script that you can use to ship Qt apps that works on all linux distros: https://github.com/probonopd/linuxdeployqt
Also, is there a particular technical reason you went with CEF directly instead of QtWebEngine or QtWebkit ? It would be interesting to know about it.
I'll look into linuxdeployqt. I am probably just going to statically link Qt. I am not using anything security conscious with Qt and I don't want versions changing underneath, so a system-level Qt makes little sense I think.
QtWebKit was deprecated then just recently undeprecated IIRC (with a non-Qt maintainer). As for the QWebEngine stuff, it was a bit premature when I was looking and didn't offer everything I needed at a low level. It's quite possible it does now (and would make my work easier!), but I have not looked.
