[Interest] What's the configure switch to have xcb working when deploying Qt apps?

[Thiago Macieira]

On Sunday, 1 October 2017 07:09:18 PDT Nikos Chantziaras wrote:
> > The plugin is listed, but couldn't be loaded. Run ldd on the plugin and
> > you'll see what libraries are missing. They need to be installed in the
> > target system by the user.
> 
> No, that wasn't it. I mean it was (technically), since ldd showed it
> depends on the xinerama library which was missing, but on the other hand
> in wasn't, since on the *build* system, ldd does not show a dep on
> xinerama. That dep only shows up on the target system. Which is weird.

You've done something wrong. The DT_NEEDED ELF header is added during the 
build. So the dependency was there on the buildsystem too.

The other option is that it's a missing indirect dependency, in which case the 
problem existed before your application was deployed to that system.

> https://github.com/qtproject/qtsdk/blob/v5.6.3-packaging/packaging-tools/bld
> _config/configure_linux_opensource
> 
> Building with those cured the problem.

The trick being -qt-xcb, which uses a bundled version of XCB instead of the 
one from the system.

Note all those -qt-libname flags. You're bundling all of them. That means 
you're accepting responsibility for monitoring them for security issues and 
updating your application if any issue is found. The first three are notorious 
for needing that.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center