[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Kword ambiguous overload / Makefile generation with qt
From:       Thomas Capricelli <capricel () enst ! fr>
Date:       1999-05-18 12:44:19
[Download RAW message or body]



Am I the only one having this problem ?

char.cc: In function `class ostream & operator <<(class ostream &, class KWString &)':
char.cc:931: ambiguous overload for `QChar & != int'
char.cc:931: candidates are: operator !=(int, int) <builtin>
/usr/src/qt/include/qstring.h:187:                 operator !=(QChar, QChar)
/usr/src/qt/include/qstring.h:198:                 operator !=(QChar, char)
/usr/src/qt/include/qstring.h:193:                 operator !=(char, QChar)
/usr/src/qt/include/qstring.h:597:                 operator !=(const QString &, const QString &)
/usr/src/qt/include/qstring.h:604:                 operator !=(const QString &, const char *)     


Also a strange but not-too-much-annoying problem related to makefile generation:
while using --with-qt-dir=/usr/src/qt, all Makefiles are generated well BUT
those in   
	kdelibs/corba/python
	kdelibs/corba/python/idl
	kdelibs/tutorials
	kdelibs/tutorials/*

Those Makefiles still use  /usr/lib/qt as path for libs and includes. I have to
change them manually everytime I update with cvsup.

Thomas

----
Thomas Capricelli	<capricel@enst.fr>
http://www.ecoledoc.lip6.fr/~capricel/

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic