On quarta-feira, 4 de maio de 2016 17:10:30 PDT Mark De Wit wrote: > Hmm, is that proving my point, though? My understanding was that compiling > Qt in a namespace and with unique filename was recommended to avoid > (minimise) the likelihood of conflicting Qt versions in a single process.
That is true, but why are you worried about this in the first place? Are you loading random plugins from other sources that may or may not be linked to Qt? If so, that's not a common use-case (hence no BKM for this). The only case that may be relevant is to deal with plugins installed by the system Linux distribution. But Qt should refuse to load plugins linked to newer versions of itself, not to mention that this is now enforced by the dynamic linker itself since Qt 5.6. In any case, the situation is often reversed, as user applications often come with Qt versions newer than the system installation. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development