> Seems that Suse has special way how to keep Qt3/4 header files.
> What is the /usr/include/QtGui/? Is it directory or link to Qt3/4
> header files directory?
>
It is a directory of the qt4 installation.

 

> My is:
> $ qmake -v
> Qmake version: 1.07a (Qt 3.3.7)
> Qmake is free software from Trolltech AS.
>
>
> qmake -v
QMake version 2.01a
Using Qt version 4.2.1 in /usr/lib

Ok, is there any qmake regarding to Qt3? 

regarding include and lib paths:
cd kpdf-kde-3.3.2 && qmake && make staticlib
make[2]: Entering directory
`/usr/src/packages/SOURCES/pdfedit-0.2.4/src/kpdf-kde-3.3.2'
g++ -c -pipe -g -O2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG
-DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/default
-I. -I/usr/include/QtCore -I/usr/include/QtCore -I/usr/include/QtGui
-I/usr/include/QtGui -I/usr/include -I../xpdf -I../xpdf/xpdf
-I../xpdf/goo -I../xpdf/splash -I../xpdf/fofi -I. -I. -o
QOutputDevPixmap.o QOutputDevPixmap.cpp
QOutputDevPixmap.cpp: In constructor
'QOutputDevPixmap::QOutputDevPixmap(Guchar*)':
QOutputDevPixmap.cpp:39: error: call of overloaded 'QImage(int)' is
ambiguous
/usr/include/QtGui/qimage.h:104: note: candidates are:
QImage::QImage(const char*, const char*)
/usr/include/QtGui/qimage.h:102: note: QImage::QImage(const QString&,
const char*)
/usr/include/QtGui/qimage.h:100: note: QImage::QImage(const char* const*)
QOutputDevPixmap.cpp: In member function 'virtual void
QOutputDevPixmap::endPage()':
QOutputDevPixmap.cpp:62: error: 'class QImage' has no member named 'reset'
QOutputDevPixmap.cpp:78: error: 'IgnoreEndian' is not a member of 'QImage'
make[2]: *** [QOutputDevPixmap.o] Fehler 1

Since it is using /usr/share/qt4/mkspecs/default as lib path, I asume,
qmake is doing this job well.

BTW, in SuSE 10.2, QTDIR is set to qt3. I changed this to qt4, but this
didn't helped.

Ok, this everything tells me, that even that you are using QTDIR set to qt3 directory,
this is not anough for proper installation. You have to use also qmake specific
for qt3 because this util sets correct include and library paths.
PDFedit is not prepared for QT4 at this moment (that is on TODO list), so try to persuade
your system to use qt3 only stuff for pdfedit compilation and everything should fork fine.

--
Michal Hocko