[QScintilla] QScintilla-1.73-gpl-2.1 problem compiling with MinGW and Qt-4.2.2

[Phil Thompson]

On Tuesday 26 June 2007 8:31 am, Max Belov wrote:
> Hi guys,
>
> I'm trying to build QScintilla with MinGW and getting the following errors:
>
> qscilexerbash.cpp: In member function `QColor
> QsciLexerBash::defaultColor(int) const': qscilexerbash.cpp:105: error: no
> matching function for call to `QsciLexerBash::defaultColor(int&) const'
> C:/Max/dev/lib/qt-4.2.2/include/Qsci/qscilexer.h:172: note: candidates are:
> virtual QColor QsciLexer::defaultColor() const qscilexerbash.cpp: In member
> function `bool QsciLexerBash::defaultEolFill(int) const':
> qscilexerbash.cpp:118: error: `defaultEolFill' is not a member of
> `QsciLexer' qscilexerbash.cpp: In member function `QFont
> QsciLexerBash::defaultFont(int) const': qscilexerbash.cpp:139: error: no
> matching function for call to `QsciLexerBash::defaultFont(int&) const'
> C:/Max/dev/lib/qt-4.2.2/include/Qsci/qscilexer.h:167: note: candidates are:
> virtual QFont QsciLexer::defaultFont() const qscilexerbash.cpp:153: error:
> no matching function for call to `QsciLexerBash::defaultFont(int&) const'
> C:/Max/dev/lib/qt-4.2.2/include/Qsci/qscilexer.h:167: note: candidates are:
> virtual QFont QsciLexer::defaultFont() const qscilexerbash.cpp: In member
> function `QColor QsciLexerBash::defaultPaper(int) const':
> qscilexerbash.cpp:269: error: no matching function for call to
> `QsciLexerBash::defaultPaper(int&) const'
> C:/Max/dev/lib/qt-4.2.2/include/Qsci/qscilexer.h:177: note: candidates are:
> virtual QColor QsciLexer::defaultPaper() const mingw32-make[1]: ***
> [debug\qscilexerbash.o] Error 1
> mingw32-make[1]: Leaving directory `C:/Max/dev/lib/QScintilla-1.73-2.1/Qt4'
> mingw32-make: *** [debug] Error 2
>
> The funny thing is that I'm looking at the code and cannot see any problem,
> but my compiler just cannot see these functions. It can be something wrong
> with GCC, but I'm not sure. If I build the component without high-level
> stuff ( QsciLexer & Co ) everything is fine, but I don't want to implement
> them myself. Have anybody met this problem before? Have anybody tried to
> compile it with GCC on Win32 at all? Any ideas how to fix?
>
> Thanking you in advance,

Have you got an earlier version installed? I think there is a problem with 
MinGW that it finds the already installed .h files before the new ones.

Phil