-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
1.0.0
-
None
-
S60 5.0 N97 emulator
Latest Qt from qt-s60-public/4.6 branch
Latest QtMobility from git://gitorious.org/qt-mobility/qt-mobility.git
-
d6ff8af6478c9492f00056f4a6e2429b09d26cff
If I configure Qt with -libinfix option, say '-qtlibinfix MyTest', all my Qt dlls/libs will have MyTest suffix. For example:
- QtCoreMyTest.dll
- QtGuiMyTest.dll
- etc
From QtMobility I did not find any possibility to define libinfix and in the other hand it does not automatically use the one defined by Qt correctly. This leads to the following problem:
1. My Qt DLLs have libinfix, f.ex. QtCoreMytest.dll
2. My QtMbility DLLs does not have libinfix, f.ex. QtBearer.dll
3. Application tries to link against libinfixed binaries (QtCoreMyTest and QtBearerMyTest) for both Qt and QtMobility, and apparently fails since QtBearerMyTest does not exist.
The bug occurs since QtMobility uses qtAddLibrary function to add mobility libraries to the project. qtAddLibrary will automatically add Qt libinfix to all libraries. To solve the issue, there are few options:
1. QtMobility should include qbase.pri from Qt, or rename mobility binaries correspondingly as Qt does:
TARGET = $$qtLibraryTarget($$TARGET$$QT_LIBINFIX) #do this towards the end
2. QtMobility should not use qtAddLibrary and thus not use libinfix logic at all
3. QtMobility can provide own libinfix mechanism
4. etc
I would prefer option 1, since it would make QtMobility libs consistent with Qt libs, and simplify integration to Qt later on.
- relates to
-
QTMOBILITY-1810 QtMobility binaries cannot be deployed when built against infixed Qt
-
- Closed
-