| Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 6 | |
We would like to build a couple of applications that may be based on different versions of Qt4. The problem now is that an application linked with 4.3.5 includes only references e.g. libQtCore.so.4. This reference would be satisfied by _any_ Qt4 QtCore library, even the existing free libraries on the system. My first idea was to ship the appropriate Qt libraries with the application and install them in a dedicated directory searched via rpath. However, this would come close to static builds, as each application needs its personal copy of the "shared" objects. The next idea is now that the Qt shared objects should include a more detailed DT_SONAME (like libQtCore.so.4.3) or are built not using the -soname flag when linking (resulting in libQtCore.so.4.3.5). Is there a configure option to achieve this? Or is there an other way to solve the potential version mismatch? Best Regards / Mit freundlichen Grüßen Rainer Wiesenfarth -- [ signature omitted ]
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
Rainer Wiesenfarth wrote: > We would like to build a couple of applications that may be based on > different versions of Qt4. The problem now is that an application linked > with 4.3.5 includes only references e.g. libQtCore.so.4. This reference > would be satisfied by _any_ Qt4 QtCore library, even the existing free > libraries on the system. [snip] > > Is there a configure option to achieve this? Or is there an other way to > solve the potential version mismatch? You might try configure's --qtlibinfix option. -- [ signature omitted ]
Christoph Duelli wrote: >> Is there a configure option to achieve this? Or is there an other way to >> solve the potential version mismatch? > You might try configure's --qtlibinfix option. I might add: this option was introduced in Qt4.4 (maybe 4.3.5 got is as well?). -- [ signature omitted ]
On Thursday 29 May 2008 14:08:39 Christoph Duelli wrote: > >> Is there a configure option to achieve this? Or is there an other way to > >> solve the potential version mismatch? > > > > You might try configure's --qtlibinfix option. > > I might add: this option was introduced in Qt4.4 (maybe 4.3.5 got is as > well?). No, that's a 4.4.0 feature. Our policy is to not add new features in patch-level releases. That also includes new symbols, so everything in the same minor series is both forwards and backwards compatible with each other. So it wasn't available when 4.3.0 was released, it'll not be available in 4.3.5 :-) -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.