Re: Additional compiler support for qpl'd Qt4/win32

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1936579153==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigDFDF177B190C402FB16CE819"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDFDF177B190C402FB16CE819
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Klaus D. G=FCnther schrieb:
> Hello,
>=20
> I use your "Additional compiler support for qpl'd Qt4/win32",
> msvc2005. I can successfully build Qt413 and our own applications,
> but when I launch Qt assistant/designer/linguist a R6034 error
> is reported saying that a program attempts to load the C
> run time library without using a manifest.
>=20
> If I use the Microsoft Dependency Walker and its profiling
> feature then it turns out that the actual reason seems to be
> that assistant/designer/linguist load the image format plugin
> dll's (gif/jpeg/mng) in their debug version: qgif1d.dll etc..
>=20
> This in turn seems to have the consequence that the debug
> versions of the main Qt dll's are loaded subsequently
> in addition to the (already loaded) release versions,
> and finally the R6034 error is reported.
>=20
> If I hide the debug versions of the image format plugin dll's
> then the error doesn't occur since then the release versions
> are loaded. But I cannot expect the users of our software
> to do this, too.
>=20
> I have another Qt4/msvc2005 installation on a second PC
> which doesn't show this behavior: assistant... loads the
> release versions of the image format plugins.
>=20
> I couldn't find out so far why on my first computer the debug
> versions are tried first.
>=20
> Might this perhaps be related to your Qt4 patches?
>=20
Sorry for the dealy.

I don't think it has something to do with the paches because we only add
the makefile-generator and don't have to change anything on the source
(at least not for msvc). I don't have an idea why this hapeend but when
you want to investigate further, maybe
qimageread.cpp:createReadHandler() is a good starting point.

Christian


--------------enigDFDF177B190C402FB16CE819
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEqYZGHAIuqbOiZ+kRAucpAJ9brNh4k7vS4yMBrwQdqMKt/RQ8UgCgsodn
rPI/AjrC7kXDu0154ADaV/c=
=rMc8
-----END PGP SIGNATURE-----

--------------enigDFDF177B190C402FB16CE819--

--===============1936579153==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-cygwin mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-cygwin

--===============1936579153==--