Qt Creator Installation - Windows XP

[SixDegrees]

QTDIR is already set as you've indicated. QTBIN wasn't, but setting it made no difference.

[Timoteo]

What does your PATH look like? I define QTBIN so that I can use it with some of my own tools and I also append it to PATH.

[SixDegrees]

I don't have that machine in front of me right now, but PATH contains QTDIR/bin, QTDIR/mingw/bin and the normal Windows-related destinations.

[Zlatomir]

What you added to EnvironmentVariables-> Path looks like this?

C:\Qt\2010.05\mingw\bin;C:\Qt\2010.05\qt\bin;

C:\Qt\2010.05\mingw\bin;C:\Qt\2010.05\qt\bin;

To copy to clipboard, switch view to plain text mode 

If so try to reverse the order, add qt first and mingw second (i don't have Xp, but i just fixed a Qt installation on a friend's computer with Windows Xp)

C:\Qt\2010.05\qt\bin;C:\Qt\2010.05\mingw\bin;

C:\Qt\2010.05\qt\bin;C:\Qt\2010.05\mingw\bin;

To copy to clipboard, switch view to plain text mode 

On my computer with Windows 7 the first line works fine.

[SixDegrees]

The path looks like your second example, with the typical Windows destination following what you've shown.

This appears to be a known issue. There's another post on this blog that precisely duplicates the problems I'm seeing (although running configure/make/make install doesn't work for me, as the build dies somewhere in Webkit) and there are a couple other similar reports on the Qt forum. No solutions to be found, but it looks like something in the Qt installer barfs on certain XP systems.

[Zlatomir]

Have you tried to download the latest source (4.7.1) and build it yourself? Hopefully it will be fixed when the new version will be packed in the SDK.

Also the errors in building Webkit with MingW are issues that i heard of many times, i never build Qt with MingW, and with VS it only gives some warnings somewhere in Webkit.

[SixDegrees]

I downloaded the SDK bundle because I wanted to avoid using VS; the problem we're trying to solve just isn't worth that level of expense or effort, although it is very frustrating that the SDK works fine on Vista but not on this particular XP system. What we're doing right now is not fun - we're building on Vista and transporting the executable and dlls over to the XP box - but it works.

I tried a couple different versions of the SDK bundle, all with the same result.

[ktk]

What happens if you don't add anything to PATH at all?