Simply remove the offending line in qwt_valuelist.h
Uwe
Simply remove the offending line in qwt_valuelist.h
Uwe
Thanks Uwe,
I tried to comment out the line, still getting the same compilation error
C:/qwt-5.1.2/../../Qt/2009.05/qt/include/QtCore/../../src/corelib/tools/qhash.h:875: error: call of overloaded 'qHash(const double&)' is ambiguous
Qt Code:
#if defined(QWT_TEMPLATEDLL) #if QT_VERSION < 0x040300 // Some compilers have problems, // without a qHash(double) implementation #include <qset.h> #include <qvector.h> inline uint qHash(double key) { return uint(key); } #endif // MOC_SKIP_BEGIN template class QWT_EXPORT QList<double>; // MOC_SKIP_END #endif // QWT_TEMPLATEDLLTo copy to clipboard, switch view to plain text mode
How can i check if QT_VERSION is taking the correct value ?
Is there any other workaround for this issue
Regards,
Im' having the same problem but in another file qhash.h. Can someone summon up, simple english, how to work around ambiguous qhash call?
c:/tools/Qt/2010.01/qt/include/QtCore/../../src/corelib/tools/qhash.h:875: error: call of overloaded 'qHash(const double&)' is ambiguous
Getting the same problem both on commandline and QT Creator
QT 4.6.1 2010.01
QWT 5.2.0
g++ 4.4.0 (gcc)
brg
Jore
svn co https://qwt.svn.sourceforge.net/svnroot/qwt/branches/qwt-5.2
Jore (1st March 2010)
SOLUTION
comment line 48 in the qwt_valuelish.h"
//template class QWT_EXPORT QList<double>;
no need to export this symbol !~!
Michael
Failed Plugin
QWT_designer_plugin5.dll uses incompatible QT library. Expected build key "Windows msvc release full", got "Windows mingw release full"
(yes, I'm a newbie)
Both the project where I want to use qwt and qwt is compiled for Release. QT is configured for mingw, I do not want to use microsoft visual studio.
What am I doing wrong?
(Why is QT expecting msvc when I run it as mingw, do I have to recompile entire QT?)
Hi
I am having exactly the same problem.
Using QT4.6.2 and mingw on win7 (the OS may be risky, but considering the fact that many XP-users have the same problem, I don't think that this is an issue).
Compiling qwt-5.2 works fine, but then the plugin does not seem to install correctly in QTDesigner. That is - it works in the "standalone" version of designer but not inside QTCreator. Here, I get the same error as Jore even though I am nowhere using msvc.
I have tried to get the newst qwt (5.3 or 6.0? the trunk from the svn) and that does not compile at all.
Does anyone know how to solve this?
Many thanks in advance!
I made it!
To get it to work, I had to recompile QTCreator. Which seems to confirm that the creator in the binaries is compiled using msvc while the rest has been compiled with mingw (or here it does not matter).
In any case, all you have to do is download the QTCreator source (from trolltech), compile it from within the running (old) creator using mingw and then start it. Don't forget to set the PATH variable as it is supposed to be and you are good to go.
This is an EXTREMELY annoying problem, although I believe there is no one to blame really. But it would be nice if it could be documented somewhere, for QT as well as for qwt!
Jore (3rd March 2010)
Thank you OverTheOcean - commenting line 48 in qwt_valuelist.h fixed this compile plroblem in MS VS2005
Ok you believe Qt creator is not able to build Qt applications with a different compiler, than the one it had been build with. I can imagine, that it is not true when you carefully avoid using the wrong libs - but anyway.This is an EXTREMELY annoying problem, although I believe there is no one to blame really. But it would be nice if it could be documented somewhere, for QT as well as for qwt!
What exactly do you expect from the documentation of a library like Qwt - a note indicating, that you shouldn't try to link binaries built from incompatible compilers ?
On Linux systems you have a distribution ( and package maintainers ) taking care of dependencies and possible incompatibilities. Even if you don't know, what you are doing you can always trust on it. Unfortunately on Windows the idea of a distribution doesn't exist. In combination with other pointless problems ( like debug/release incompatibilities or this __declspec stuff, what was the reason for the qHash problem ) Windows is by far the most difficult development environment - what can be seen easily from the number of problems reported here.
Uwe
PS: Please start a new thread if you want to discuss something different. Nobody will expect to find your hint in a thread about qHash.
Bookmarks