Is is possible to link a customized static libraries to dynamic libarries of LibQtCore and libQtGui?
I have a internal memory manager code , which is made as statically linked library . is is possible to link a customized static libraries to dynamic libarries of LibQtCore and libQtGui
If you mean linking your application against static and dynamic dependencies, then yes you can.
This post is deleted!
No I have a application in which I have libqwt.so and then have libQtCore. and libQtGui.a I have source code of qwt . When I make the dynamic libaray of libqwt.so at that time can specify It can link to static libraries libQtCore. and libQtGui.a I
Then you have a static build of Qt, in that case use that version of Qt to build Qwt.
I tried the my tool crahes I did following steps
1)checkout code for qwt from my central repositry
- It is for linux centos platform
- set the qmake path where Qt Static libs have been built
setenv PATH "path to qmake where where Qt Static libs have been built"
- build the dynamic libraries
but in this case my tools crahes
One very basic question , If I have memory manger which is made as static library
- libgui.a application gui code is static library
- we are using shared libraries of .so libQtgui.so , libQtCore.so , libqwt.so libscintilla.so
What do you mean by crash ?
Segmentation fault . i want to make
- Shared libraries QWt and Qscintilla an it should not depend on /include the code of QtCore and QtGui
- Static libraries QWt and Qscintilla an it should not depend on /include the code of QtCore and QtGui
If i give
#QT -= gui core
#LIBS -= -lQtGui -lQtCore
option in qwtconfig.pri then my compliation for qwt fails
I already told you in your previous thread not to do that! What you're attempting is to duplicate the symbols (i.e. putting
scintilla) and then link both of those shared objects.
It's a mess! Symbols are getting hidden silently (or overwritten on Linux), globals are duplicated (or overwritten on Linux) and initialized in different binaries (without guarantee for order of initialization) ...
Even if you're able to make it work on Linux, which I really doubt, the moment you switch to Windows you're going to be neck deep in horse sh*t ...
To add to @kshegunov, if you don't want any code from Qt in Qwt and Qsinctilla, why are you using them in the first place ?
I will a final executable in which libQtCore.a and libQGui.a and I will libQwt.so and libQscintall.so and as I mentioned the requirement is to make libQwt.so and libQscintall.so without having dependency on libQCore.so and libQtGui.so
Oh, boy ...