[quote author="MamdouhAlShamy" date="1292336841"]unfortunately YES[/quote]
Then probably you are missing something when packaging it. I dont have much idea about WM Qt. Hope someone more experienced responds to this thread.
You can always download latest source from qt, get build file from repo, update it (in most cases it will be just bumping version) and create own package.
[quote author="kryptobs2000" date="1292168911"]Yeah, that's where it came from then. I think I may even have two copies of mingw sitting around, probably not the best idea (though only 1 is on the path I believe). So should I uninstall mingw? I didn't think Qt came with mingw, which I take it you're implying should have been installed for me?[/quote]
The Qt SDK comes with mingw. The binary Qt distribution does not.
Thanks! Although I have to admit, I haven't really done very much which would qualify as "help" - mostly all I did was take the existing Debian rules and munge them to build "~gcs0+lucid" and "~gcs0+maverick" builds. I did write the Debian stuff for Qt Components, though, so you're right, I really should send that up as an MR. :)
My error - apparently qmake only does that for Unix-style Makefiles...
So amending that, just change into that directory and run:
@qmake -o Makefile.Debug WebCore.pro -d -d >qmake.dbg 2>&1@
good job, fifth. :-)
As you've seen in the comments, the file you mentioned is part of libjpeg. So, the solution from Qt's perspective is to set NO_GETENV. I think libjpeg developers will like to know about this issue.
[quote author="theuser" date="1291768946"]edit: ah and thank you for the link to the newer tutorials i didnt know the one i worked with was "out of date"(though i guess the basic concepts are still the same)[/quote]
Indeed, the concepts are still the same. Also, it is a Qt 4 example so it is expected to work with Qt 4.7 too.
I just pointed it's old because I could not find in the Qt 4.7 sources :-P
Thanks Tobias!
Removing the Shadow-build check in the Projects Building Settings for Release and Debug made the trick.
I have tried three different Examples and they all run fine.
/Mike
PS. Sorry folr the missing back slashes. They got lost somewhare between copying the Compiler output to the pais into this forum. Possible the forum security does not alow them to prevent execution of mallisious code through this web site? DS.
[quote author="infoctopus" date="1291576301"]you could try VS2008 Express. If the problems persists, then it's maybe a Express edition issue Also reinstalling Windows can be of ultimate help ;) (since it's all fine on clean virtual Win7)[/quote]
No, thanks, maybe next time :)
I can survive with Qt SDK in Ubuntu under VirtualBox.
I am not sure which version it was as I had vs.net (academic version - full install), visual studio 2005 c++ express, vs 2008 c++ express, vs 2010 c++ express. I think it was the number of different vs installs that caused the problem.
Well blex, you were not right but you led me to the answer. It wasn't the drive letter but the VS2008 install. I have been using a non-standard install of VS2008 to compile Qt but it no longer builds Qt 4.7.1 for x86 targets. A standard VS2008 install works fine.