Serghei,
The kdevelop build is failing on the last line of
kdevdesigner/designer/kdevdesigner_part.cpp with the
#include "kdevdesigner_part.moc"
The error generated is:
kdevdesigner/designer/kdevdesigner_part.cpp:563:33: fatal error:
kdevdesigner_part.moc
Does this need to be fixed in the code, or is it a build error on my end?
--
David C. Rankin, J.D.,P.E.
Tim,
Here are a bunch of patches I don't think have been merged into Trinity.
http://humanreadable.nfshost.com/trinity/patches/
I checked them against svn (my head hurts!). I might have missed a few because of the changes to run through tqtinterface, but not many if I did.
Some of them will need to be converted to using TQT.
I found these patches while building KDE 3.5.10 on Slackware 13.1. There were many more patches, but those I did not post have been merged into Trinity.
There are quite a few patches against qt3. Several apps include patches for libpng 1.4.
Darrell
Baho - and others interested in packaging specifics,
In the kdebase PKGBUILD, I handled packaging of kdmrc and the Xsession file
as follows:
# set kdm directory
_kdmdir=${trinity_prefix}/share/config/kdm
[[ -d ${pkgdir}/${_kdmdir} ]] || install -d -m755 ${pkgdir}/${_kdmdir}
# install kdmrc
[[ -f kdmrc ]] && install -m644 kdmrc ${pkgdir}/${_kdmdir}
# update the Xsession file
[[ -f Xsession ]] && install -m755 Xsession ${pkgdir}/${_kdmdir}
# create the starttrinity link
[[ -d ${pkgdir}/usr/bin ]] || mkdir -p ${pkgdir}/usr/bin
cd ${pkgdir}/usr/bin
ln -sf /opt/trinity/bin/startkde starttrinity
You handled it slightly differently, primarily using cp and chmod instead of
install and adding the 'n' option to the link of starttrinity:
_kdmdir=${_prefix}/share/config/kdm
[[ -d ${pkgdir}/${_kdmdir} ]] || install -d -m755 ${pkgdir}/${_kdmdir}
[[ -f kdmrc ]] && cp -v kdmrc ${pkgdir}/${_kdmdir}
[[ -f ${scrdir}/Xsession ]] && {
cp -v ${scrdir}/Xsession ${pkgdir}/${_kdmdir}
chmod 0755 ${pkgdir}/${_kdmdir}/Xsession
}
[[ -d ${pkgdir}/usr/bin ]] || mkdir -p ${pkgdir}/usr/bin
ln -snf startkde ${pkgdir}/usr/bin/starttrinity
What is the benefit of using cp + chmod instead of 'install -m'? Also, why the
'ln -snf' on starttrinity instead of just 'ln -sf'? Just habit or convention? On
both, I'm just curious. If the cp + chmod is less problematic, then that's the
way I want to go, but I don't want to just dismiss the use of install without
understanding the benefit.
What says the master?
--
David C. Rankin, J.D.,P.E.
Guys,
I am having problems with poppler-qt3 on arch. I suspect I have missed
something in Qt3. Basically, I think the build fails due to a lack of qt-mc.pc
package config information:
configure:21231: $PKG_CONFIG --exists --print-errors "qt-mt"
Package qt-mt was not found in the pkg-config search path.
Perhaps you should add the directory containing `qt-mt.pc'
to the PKG_CONFIG_PATH environment variable
No package 'qt-mt' found
configure:21234: $? = 1
configure:21247: $PKG_CONFIG --exists --print-errors "qt-mt"
Package qt-mt was not found in the pkg-config search path.
Perhaps you should add the directory containing `qt-mt.pc'
to the PKG_CONFIG_PATH environment variable
No package 'qt-mt' found
configure:21250: $? = 1
configure:21263: result: no
No package 'qt-mt' found
configure:21280: error: in `/home/david/tblds/poppler-qt3/src/poppler-0.16.4':
configure:21282: error: Qt development libraries not found
So far tqtinterface, arts and pyqt3 have all built fine. Where does one
usually install the qt-mc.pc file from? The Qt3 install?
--
David C. Rankin, J.D.,P.E.
Hi,
my name is Simon. I'm from germany and want to help!
I can offer: C/C++ Programming skills, some spare time and a web-server with
some (not much) free bandwidth.
I am particularly interested in the openSuSE support.
--
Mit freundlichen Grüßen
Simon Brennecke
http://www.brennecke-it.net/simon
simon(a)brennecke-it.net
ICQ#: 333419168
Guys,
Here is the error I get attempting to build tqtinterface with the new Qt:
==> Starting cmake...
-- Checking for Qt3...
-- QT_PREFIX_DIR is set to QTDIR
-- QT_PREFIX_DIR : /opt/qt
-- QT_INCLUDE_DIR: /opt/qt/include
-- QT_LIBRARY_DIR: /opt/qt/lib
-- QT_BINARY_DIR : /opt/qt/bin
-- MOC_EXECUTABLE: /opt/qt/bin/moc (using Qt 3.3.8c)
-- UIC_EXECUTABLE: /opt/qt/bin/uic
CMake Error at cmake/modules/TDEMacros.cmake:20 (message):
#################################################
Unable to build a simple Qt3 test.
#################################################
Call Stack (most recent call first):
ConfigureChecks.cmake:167 (tde_message_fatal)
CMakeLists.txt:29 (include)
-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
Aborting...
What is this test checking and how can I be failing it?
--
David C. Rankin, J.D.,P.E.
Guys,
Just a check. I'm still pulling the svn code from
svn://anonsvn.kde.org/home/kde/branches/trinity/... With all the
trinitydesktop.org additions, I just thought I would check to make sure that is
still the correct place for the svn code.
So we are still just putting the distribution build files on
trinitydesktop.org and the actual code is still on anonsvn.kde.org -- right?
--
David C. Rankin, J.D.,P.E.
Guys,
I have finally gotten a few minutes to dive back into Trinity. To my chagrin,
we have Arch has bumped from gcc 4.5 to gcc 4.6. I am having problems building
Qt3. Adding to the difficulty, the Qt3 build script for Arch has been through a
number of changes lately and I haven't had time to verify the new build script
under gcc 4.5 before the jump to gcc 4.6. So I am working to understand whether
this build failure is gcc related or if it is a normal screw-up on my end.
The build is failing in the middle of the build, so this leads me to think
this might be gcc related. If anybody can look at the error and determine
whether this is a gcc issue or not, I would greatly appreciate it. I think what
I'll do is drop back to a build script that I know was working on gcc 4.5 and
confirm, but in the interim, I thought I would post the error in hope somebody
else had seen this already. What does this error look like to the masters?:
g++ -c -pipe -Wall -W -march=i686 -mtune=generic -O2 -pipe -D_REENTRANT -fPIC
-DQT_SHARED -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT
-D_LARGEFILE_SOURCE -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -DQT_NO_IMAGEIO_MNG
-DQT_NO_IMAGEIO_JPEG -DQT_NO_IMAGEIO_PNG -DQT_BUILTIN_GIF_READER=1
-DQT_NO_STYLE_MAC -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_INTERLACE
-DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_COMPACT -DQT_NO_STYLE_POCKETPC
-I/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b/mkspecs/linux-g++ -I.
-I/usr/include/freetype2 -I3rdparty/opentype -I../include -I/usr/X11R6/include
-I/usr/X11R6/include -I.moc/release-shared-mt/ -o
.obj/release-shared-mt/qapplication_x11.o kernel/qapplication_x11.cpp
In file included from ../include/qmap.h:49:0,
from kernel/qmime.h:46,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qvaluelist.h:91:13: error: ‘ptrdiff_t’ does not name a type
../include/qvaluelist.h:167:13: error: ‘ptrdiff_t’ does not name a type
In file included from ../include/qmap.h:49:0,
from kernel/qmime.h:46,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qvaluelist.h:427:13: error: ‘ptrdiff_t’ does not name a type
In file included from kernel/qmime.h:46:0,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qmap.h:110:13: error: ‘ptrdiff_t’ does not name a type
../include/qmap.h:226:13: error: ‘ptrdiff_t’ does not name a type
In file included from kernel/qmime.h:46:0,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qmap.h:607:13: error: ‘ptrdiff_t’ does not name a type
kernel/qapplication_x11.cpp: In member function ‘int
QApplication::x11ProcessEvent(XEvent*)’:
kernel/qapplication_x11.cpp:3693:54: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp:3706:54: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In member function ‘bool
QETWidget::translateMouseEvent(const XEvent*)’:
kernel/qapplication_x11.cpp:4122:30: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In member function ‘bool
QETWidget::translateKeyEventInternal(const XEvent*, int&, QString&, int&, char&,
int&, QEvent::Type&, bool)’:
kernel/qapplication_x11.cpp:5161:8: warning: suggest explicit braces to avoid
ambiguous ‘else’ [-Wparentheses]
kernel/qapplication_x11.cpp:5232:52: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp:5235:52: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In function ‘int isPaintOrScrollDoneEvent(Display*,
XEvent*, XPointer)’:
kernel/qapplication_x11.cpp:5524:34: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
make[2]: *** [.obj/release-shared-mt/qapplication_x11.o] Error 1
make[2]: Leaving directory
`/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b/src'
make[1]: *** [sub-src] Error 2
make[1]: Leaving directory `/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b'
make: *** [init] Error 2
==> ERROR: A failure occurred in build().
Aborting...
I'll go try an older build script that used qt-x11-free-3.3.8 instead of
qt-x11-free-3.3.8b. I'll report back :p
--
David C. Rankin, J.D.,P.E.