|
From: | Mark Brand |
Subject: | Re: [Mingw-cross-env-list] Qt libjscore.a not installed |
Date: | Thu, 08 Dec 2011 23:36:27 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:8.0.1) Gecko/20111121 Firefox/8.0.1 SeaMonkey/2.5 |
Hi Gareth, Hope you don't mind my CCing the list in my reply. G Coco wrote:
On Tue, Dec 6, 2011 at 3:21 AM, Mark Brand<address@hidden> wrote:Looks like it may be back to DLL's for me.Are you thinking of just building all of Qt as shared libraries? You might try building just QtWebKit as a DLL.How would be the best way to do this within the MCE environment. That would be a good compromise for me in this.
Unfortunately, I think that was a misguided suggestion on my part. QtWebKit depends on several other Qt libraries. If you build QtWebKit as a DLL and the others static, you'll end up embedding them all into the QtWebKit DLL, which is probably not what you want.
If you still want to pursue this, I think you'll have to hack in the relevant project files (.pro/.pri).
Using shared Qt libs looks like the only known solution for linking an application to both QtWebKit and QtScript at this point.
It's possible to build a usable shared Qt with mingw-cross-env. I used to do it regularly several version ago. Just remove "-static" from the configure options in qt.mk. You'll still end up with dependencies like zlib, jpeg, png, openssl, postgresql, etc (static in mingw-cross-env) embedded in the Qt DLLS, but that's probably tolerable. You might want to disable the features you don't need to keep this at a minimum.
Keep in mind the defaults for Qt image format and SQL drivers. The default is plugin for shared Qt and built-in for static Qt. There are configure options to override the defaults.
Mark
[Prev in Thread] | Current Thread | [Next in Thread] |