After kdebase - pykde3 build complains about dcopobject.sip - Worry about it -- or move on?
16 Feb
2011
16 Feb
'11
3:41 a.m.
Tim, All,
After getting kdebase done, I had planned to do pykde3 and make a stab at
kdebindings. I know they are not required, but I wanted to see if I could make
some headway. Alas - not much :(
It looks like the pykde3 dcopobject.sip included in the latest pykde3 package
is not happy with TQt:
<snip>
Creating top level Makefile...
Creating pykdeconfig.py...
make[1]: Entering directory `/home/david/tbld/pykde3/src/PyKDE-3.16.7/dcop'
g++ -c -Wno-deprecated-declarations -pipe -fPIC -march=i686 -mtune=generic -O2
-pipe -Wall -W -D_REENTRANT -DNDEBUG -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I.
-I../extra/kde353 -I/opt/trinity/include -I/opt/qt/include/tqt
-I/usr/include/python2.7 -I/opt/qt/mkspecs/default -I/opt/qt/include
-I/usr/X11R6/include -o sipdcoppart0.o sipdcoppart0.cpp
In file included from sip/dcop/dcopobject.sip:30:0:
/opt/trinity/include/dcopobject.h:35:9: error: ‘TQValueList’ does not name a type
/opt/trinity/include/dcopobject.h:80:23: error: expected ‘)’ before ‘*’ token
/opt/trinity/include/dcopobject.h:85:20: error: ‘TQCString’ does not name a type
/opt/trinity/include/dcopobject.h:85:31: error: ISO C++ forbids declaration of
‘objId’ with no type
/opt/trinity/include/dcopobject.h:96:3: error: ‘TQCString’ does not name a type
<snip>
Full build output:
http://www.3111skyline.com/dl/dt/trinity/errors/pykde3-err-i686.txt
Question is - should we spend any more time worrying about it or just move on
to kdeaccessibility? (kdebindings still doesn't find TQt or any kde libraries)
kdebindings err:
<snip>
checking if TQt is available... no
configure: WARNING: You are attempting to compile Trinity without the Trinity Qt
Interface installed. Please install libtqtinterface-dev and try again!
checking if Qt needs -ljpeg... no
checking for rpath... yes
checking for KDE... configure: error:
in the prefix, you've chosen, are no KDE libraries installed. This will fail.
So, check this please and use another prefix!
Aborting...
<snip>
Full kdebindings output:
http://www.3111skyline.com/dl/dt/trinity/errors/kdebindings-no-kde-libs.txt
I've tried:
--with-extra-libs=${trinity_prefix}/lib
--with-extra-libs=${trinity_prefix}/lib/kde
with and without:
--disable-rpath
I don't get it?
I don't know how important these things are. What say the experts? Move on and
come back later?
--
David C. Rankin, J.D.,P.E.
16 Feb
16 Feb
4:01 a.m.
New subject: [trinity-users] After kdebase - pykde3 build complains about dcopobject.sip - Worry about it -- or move on?
On 02/15/2011 09:41 PM, David C. Rankin wrote:
checking for KDE... configure: error:
in the prefix, you've chosen, are no KDE libraries installed. This will fail.
So, check this please and use another prefix!
Aborting...
<snip>
kdeaccessibility gives the same error. Maybe I'm screwing up the configure? I'm
prepping and configuring as follows:
cd ${startdir}
cp -Rp /usr/share/aclocal/libtool.m4 admin/libtool.m4.in
cp -Rp /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
make -f admin/Makefile.common
# set --enable-closure configure option if needed (needed for kdeaccessibility)
trinity_prefix="/opt/trinity"
./configure --prefix=${trinity_prefix} \
--includedir=${trinity_prefix}/include/kde \
--mandir=${trinity_prefix}/share/man \
--infodir=${trinity_prefix}/share/info \
--with-extra-libs=${trinity_prefix}/lib/kde3 \
--sysconfdir=/etc \
--localstatedir=/var \
--libexecdir=${trinity_prefix}/lib/kde3 \
--disable-rpath \
--with-xinerama \
--with-qt-dir=/opt/qt \
--with-qt-includes=/opt/qt/include \
--with-qt-libraries=/opt/qt/lib \
--with-extra-includes=/opt/qt/include/tqt \
--enable-closure
cd ${srcdir}
make || return 1
Does anybody see anything glaringly wrong with how I'm trying to setup the build
for either kdebinding or kdeaccessibility? It looks like I'm screwing up
--prefix, but I can't understand how?
HowToBuild says the build order is:
* tqtinterface
* arts
* kdelibs
* kdebase
* kdebindings (not required for a working Trinity environment)
The following build order seems to work well for the remaining core packages:
* kdeaccessibility
* kdeutils
* kdemultimedia
* kdenetwork
I've made it through kdebase:
21:59 trinity:~> pmq | grep trinity
trinity-qt3 3.3.8-20
trinity-pyqt3 3.18.1-9
trinity-tqtinterface 1220969-1.0
trinity-arts 1220969-1.1
trinity-kdelibs 1220969-1.1
trinity-kdebase 1220975-1.0
but after that things are presenting a bit more challenge ;-) Where do I need
to focus my attention in the build order next?
--
David C. Rankin, J.D.,P.E.
4:06 p.m.
New subject: [trinity-users] After kdebase - pykde3 build complains about dcopobject.sip - Worry about it -- or move on?
On 02/15/2011 09:41 PM, David C. Rankin wrote:
<snip>
Hmm...you're using CMake to build kdelibs/kdebase, correct? You can't mix
CMake and Automake, it won't work.
If kdeaccessibility does not yet have CMake available, then it can't be
built on your system at this time. We need more people to help with the
CMake port (from what I hear it is relatively simple/mind numbing work).
Tim
checking for KDE... configure: error:
in the prefix, you've chosen, are no KDE libraries installed. This will
fail.
So, check this please and use another prefix!
Aborting...
<snip>
kdeaccessibility gives the same error. Maybe I'm screwing up the
configure? I'm
prepping and configuring as follows:
cd ${startdir}
cp -Rp /usr/share/aclocal/libtool.m4 admin/libtool.m4.in
cp -Rp /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
make -f admin/Makefile.common
# set --enable-closure configure option if needed (needed for
5:10 p.m.
New subject: [trinity-users] After kdebase - pykde3 build complains about dcopobject.sip - Worry about it -- or move on?
On 02/16/2011 10:06 AM, Timothy Pearson wrote:
<snip>
Hmm...you're using CMake to build kdelibs/kdebase, correct? You can't mix
CMake and Automake, it won't work.
If kdeaccessibility does not yet have CMake available, then it can't be
built on your system at this time. We need more people to help with the
CMake port (from what I hear it is relatively simple/mind numbing work).
Tim
There is no CMake for a majority of the Trinity modules:
11:07 archangel:~/arch/trinity> for i in $(ls); do [[ -f $i/CMakeLists.txt ]]
&&
echo " CMake -- $i" || echo "NO CMake -- $i"; done | sort
CMake -- kdebase
CMake -- kdelibs
CMake -- kdevelop
CMake -- kdewebdev
NO CMake -- applications
NO CMake -- dependencies
NO CMake -- kde-common
NO CMake -- kde-i18n
NO CMake -- kdeaccessibility
NO CMake -- kdeaddons
NO CMake -- kdeadmin
NO CMake -- kdeartwork
NO CMake -- kdebindings
NO CMake -- kdeedu
NO CMake -- kdegames
NO CMake -- kdegraphics
NO CMake -- kdemultimedia
NO CMake -- kdenetwork
NO CMake -- kdepim
NO CMake -- kdesdk
NO CMake -- kdetoys
NO CMake -- kdeutils
NO CMake -- konstruct
NO CMake -- libraries
I don't know cmake from shinola, but if you have a cheat-sheet on how to
convert things to cmake, I'm happy to peck it into the keyboard. Something like
"A Dummy's Guild to Port Trinity to CMake"?
--
David C. Rankin, J.D.,P.E.
4:04 p.m.
New subject: [trinity-users] After kdebase - pykde3 build complains about dcopobject.sip - Worry about it -- or move on?
<snip>
What say the experts? Move
on and
come back later?
--
David C. Rankin, J.D.,P.E.
Yes! kdebindings is not required, and has known problems building from
SVN at this time. These issues will be fixed before 3.5.13 is released.
Tim
5:14 p.m.
New subject: [trinity-users] After kdebase - pykde3 build complains about dcopobject.sip - Worry about it -- or move on?
On 02/16/2011 10:04 AM, Timothy Pearson wrote:
Yes! kdebindings is not required, and has known
problems building from
SVN at this time. These issues will be fixed before 3.5.13 is released.
Tim
I guess the big question is "When can I try to launch Trinity?" I see kdebase
provides startkde. Looking at what remains to be ported, I guess I should be
able to launch Trinity now. Am I thinking straight? It should run without having
to build the following right?
CMake -- kdevelop
CMake -- kdewebdev
NO CMake -- applications
NO CMake -- dependencies
NO CMake -- kde-common
NO CMake -- kde-i18n
NO CMake -- kdeaccessibility
NO CMake -- kdeaddons
NO CMake -- kdeadmin
NO CMake -- kdeartwork
NO CMake -- kdebindings
NO CMake -- kdeedu
NO CMake -- kdegames
NO CMake -- kdegraphics
NO CMake -- kdemultimedia
NO CMake -- kdenetwork
NO CMake -- kdepim
NO CMake -- kdesdk
NO CMake -- kdetoys
NO CMake -- kdeutils
NO CMake -- konstruct
NO CMake -- libraries
I'll give it a shot. Let me know if I'm way off. Thanks.
--
David C. Rankin, J.D.,P.E.
4828
days inactive
4828
days old
5 comments
2 participants
participants (2)
-
David C. Rankin -
Timothy Pearson