[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Qt static codec dependencies

From: Nikos Chantziaras
Subject: Re: [Mingw-cross-env-list] Qt static codec dependencies
Date: Wed, 29 Jun 2011 12:54:44 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110624 Thunderbird/3.1.11

On 06/29/2011 12:33 PM, Mark Brand wrote:
On 06/29/2011 09:03 AM, Mark Brand wrote:

On 06/29/2011 01:34 AM, Volker Grabsch wrote:
Nikos Chantziaras schrieb:
On 06/28/2011 07:54 PM, René Berber wrote:
Nikos Chantziaras wrote:

Hold on, plugins only work if your application uses dynamic linking
No, the above is specifically for static Qt builds. It won't work
with a shared Qt. See:

Note that our tutorial points to almost the same site:

"Step 5c: Cross compile your Project (Qt)"

That's right. But the difference now is that QtCore itself introduces
dependencies on those codec plugins, so *all* Qt applications will
need to do this. This might be puzzling to people trying
mingw-cross-env for the first time. I'm thinking about ways to improve
the situation.

I think I have a good solution for this.


The static codec plugin dependencies now come automatically with QtCore
so the the user doesn't not have to worry about this for each application.

Comments are welcome.

I'd go with whatever upstream does by default. If this is a cherrypick of an upstream Git commit, then I guess it's OK. If not, then the user should have to worry about this for each application, because that's what's expected with static Qt builds; cross-env should not change expected, documented behavior.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]