Should we report Qt3 bugs or has all focus now shifted to TQt3?
Yesterday I successfully built all of my packages against TQt3. Today I tried to build against Qt3 and tdebase failed with the following:
/dev/shm/tdebase.build/kicker/kicker/core/kmenubase.ui.h:7: error: 't_xdisplay' was not declared in this scope
Reports these errors or abandon building against Qt3?
Darrell
Tim, Darrell,
Things are getting worse instead of better :) The build now craters at
tdelibs. This is with a brand new git pull and a fresh build environment. The
error looks like our friend tqt_cast is not behaving:
[ 3%] Building CXX object tdefx/CMakeFiles/tdefx-shared.dir/kdrawutil.cpp.o
[ 4%] Building CXX object tdefx/CMakeFiles/tdefx-shared.dir/kstyle.cpp.o
/build/src/tdelibs/tdefx/kstyle.cpp: In member function 'virtual void
KStyle::polish(TQWidget*)':
/build/src/tdelibs/tdefx/…
[View More]kstyle.cpp:266:25: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:266:45: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:266:47: error: expected primary-expression
before '>' token
/build/src/tdelibs/tdefx/kstyle.cpp: In member function 'virtual void
KStyle::unPolish(TQWidget*)':
/build/src/tdelibs/tdefx/kstyle.cpp:287:25: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:287:45: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:287:47: error: expected primary-expression
before '>' token
/build/src/tdelibs/tdefx/kstyle.cpp: In member function 'virtual bool
KStyle::eventFilter(TQObject*, TQEvent*)':
/build/src/tdelibs/tdefx/kstyle.cpp:1905:17: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:1905:36: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:1905:37: error: expected primary-expression
before '>' token
/build/src/tdelibs/tdefx/kstyle.cpp:1912:25: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:1912:48: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:1912:49: error: expected primary-expression
before '>' token
/build/src/tdelibs/tdefx/kstyle.cpp: In member function 'void
{anonymous}::TransparencyHandler::blendToPixmap(const TQColorGroup&, const
TQWidget*)':
/build/src/tdelibs/tdefx/kstyle.cpp:2295:6: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:2295:29: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:2295:30: error: expected primary-expression
before '>' token
/build/src/tdelibs/tdefx/kstyle.cpp:2296:48: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:2296:71: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:2296:72: error: expected primary-expression
before '>' token
/build/src/tdelibs/tdefx/kstyle.cpp: In member function 'void
{anonymous}::TransparencyHandler::XRenderBlendToPixmap(const TQWidget*)':
/build/src/tdelibs/tdefx/kstyle.cpp:2317:6: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:2317:29: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:2317:30: error: expected primary-expression
before '>' token
/build/src/tdelibs/tdefx/kstyle.cpp:2319:7: error: '::tqt_cast' has not been
declared
/build/src/tdelibs/tdefx/kstyle.cpp:2319:30: error: expected primary-expression
before '*' token
/build/src/tdelibs/tdefx/kstyle.cpp:2319:31: error: expected primary-expression
before '>' token
make[2]: *** [tdefx/CMakeFiles/tdefx-shared.dir/kstyle.cpp.o] Error 1
make[1]: *** [tdefx/CMakeFiles/tdefx-shared.dir/all] Error 2
make: *** [all] Error 2
--
David C. Rankin, J.D.,P.E.
[View Less]
Hey guys,
I was hacking on a KCM module and found that there was already a TODO
list made up for kcontrol, maybe we can exctract some ideas for that
"this file contain a list of various major changes for
KControl(reorganization, broad technical changes etc.) planned for
KDE4."
the file is located in tdebase/kcontrol/TODO
Calvin
Tim, Darrell, all
I moved tde-packaging to my laptop (kde 3.5.10 on opensuse) and went to update
it and kwallet Qt4 appeared - what the heck? I did it three times to makes sure.
Here is the konsole output I received:
22:41 alchemy:~/tde/tde-packaging> ../scr/gituppkg.sh
Checking out files: 100% (22574/22574), done.
HEAD is now at f635b71 Fix tdelibs FTBFS on Ubuntu
QDBusConnection: name 'org.kde.kwalletd' had owner '' but we thought it was ':1.35'
HEAD is now at f635b71 Fix tdelibs FTBFS …
[View More]on Ubuntu
22:41 alchemy:~/tde/tde-packaging> ../scr/gituppkg.sh
HEAD is now at f635b71 Fix tdelibs FTBFS on Ubuntu
HEAD is now at f635b71 Fix tdelibs FTBFS on Ubuntu
22:42 alchemy:~/tde/tde-packaging> ../scr/gituppkg.sh
HEAD is now at f635b71 Fix tdelibs FTBFS on Ubuntu
ksshaskpass(8692)/kdeui (Wallet): The kwalletd service has been disabled
ksshaskpass(8692)/kdeui (Wallet): The kwalletd service has been disabled
ksshaskpass(8692)/kdeui (Wallet): The kwalletd service has been disabled
ksshaskpass(8692)/kdeui (Wallet): The kwalletd service has been disabled
ksshaskpass(8692)/kdeui (Wallet): The kwalletd service has been disabled
ksshaskpass(8692)/kdeui (Wallet): The kwalletd service has been disabled
Already up-to-date.
HEAD is now at f635b71 Fix tdelibs FTBFS on Ubuntu
How is this possible? Is this supposed to happen? It was really kind of
creepy. Here is a screenshot:
http://www.3111skyline.com/dl/dt/trinity/ss/updt-packageing-launches-kwalle…
Up to this point all of the git sources have been on my server where I simply
access them via ssh. The gituppkg.sh script is simply:
cat ../scr/gituppkg.sh
#!/bin/bash
git reset --hard HEAD
git clean -dxf
git pull
git reset --hard HEAD
git clean -dxf
git submodule init
git submodule update --recursive
git submodule foreach --recursive "git checkout master"
git submodule foreach --recursive "git pull"
What's going on?
--
David C. Rankin, J.D.,P.E.
[View Less]
>
> On 03/09/2012 09:34 PM, Darrell Anderson wrote:
>
> > Configure seems okay but make stumbles with creating qt-watch.moc3.
> >
> > "moc: Too many input files specified" seems to be one of those error
message that nobody on the planet helps with. Lots of people asking, nobody
explaining. Of course, all of these non-answers are replicated a couple
hundred times all over the web. Google is a POS the past couple of years.
> >
[...]
>
> No Joy, same …
[View More]error...
>
> But HELL YA! on the rest :)
>
> I'm going to try a couple more packages on your list and then clean up
the
> build script and set up logging. Total build to 1:59 minutes on my end for
all
> the listed packages -- that's really good.
>
There is an error in avahi-tqt/Makefile.am, the qt-watch.moc3 target should
be:
$(AM_V_GEN)$(MOC_QT3) $^ -o $@
Too bad the build breaks immediately after because the tqt header path is
hardcoded to /usr/include/tqt :(
Regards,
Leandro
--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it: http://www.email.it/f
Sponsor:
Weekend di Pasqua di gusto con gli itinerari enogastronomici
nell'entroterra romagnolo proposti da Costahotels, soggiorno + escursioni
tutto compreso
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=12195&d=20120310
--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
Sponsor:
Conto Arancio al 4,20%. Soldi sempre disponibili, zero spese, aprilo in due minuti!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11923&d=10-3
[View Less]
Tim, Darrell, all,
The final package for the night is tdepim. Build up to 11% complete went
smooth. The we hit what looks like at TQt error in kscoringeditor.cpp. The build
fails with the following error:
[ 11%] Building CXX object
libtdepim/CMakeFiles/tdepim-shared.dir/kscoringeditor.cpp.o
cd /build/src/build/libtdepim && /usr/bin/c++ -Dtdepim_shared_EXPORTS
-D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -march=x86-64 -mtune=generic -O2 -pipe
-fstack-protector --param=ssp-buffer-size=4 -…
[View More]D_FORTIFY_SOURCE=2
-DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -fPIC
-I/build/src/build/libtdepim -I/build/src/build -I/build/src/tdepim
-I/build/src/tdepim/libtdepim -I/opt/trinity/include -I/opt/tqt3/include
-I/opt/trinity/include/tqt -o
CMakeFiles/tdepim-shared.dir/kscoringeditor.cpp.o -c
/build/src/tdepim/libtdepim/kscoringeditor.cpp
/build/src/tdepim/libtdepim/kscoringeditor.cpp: In member function 'void
SingleConditionWidget::showRegExpDialog()':
/build/src/tdepim/libtdepim/kscoringeditor.cpp:140:91: error: 'class TQDialog'
has no member named 'tqt_cast'
make[2]: *** [libtdepim/CMakeFiles/tdepim-shared.dir/kscoringeditor.cpp.o] Error 1
make[2]: Leaving directory `/build/src/build'
make[1]: *** [libtdepim/CMakeFiles/tdepim-shared.dir/all] Error 2
make[1]: Leaving directory `/build/src/build'
make: *** [all] Error 2
It appears that some type case named 'tqt_cast' ( hmm.. those letters sound
like something related to Pearson, don't they :) Anyway, I'm stuck and need a
bit of help from the masters to see me through. The way I approached building
tdepim was a simple cmake setup:
msg "Starting cmake..."
cmake ${srcdir}/${pkgname#*-} \
-DCMAKE_VERBOSE_MAKEFILE=ON \
-DCMAKE_INSTALL_PREFIX=$TDEDIR \
-DWITH_ALL_OPTIONS=ON \
-DBUILD_ALL=ON
The code complained of in kscoringeditor.cpp is:
void SingleConditionWidget::showRegExpDialog()
{
TQDialog *editorDialog =
KParts::ComponentFactory::createInstanceFromQuery<TQDialog>(
"KRegExpEditor/KRegExpEditor" );
if ( editorDialog ) {
KRegExpEditorInterface *editor = static_cast<KRegExpEditorInterface *>(
editorDialog->tqt_cast( "KRegExpEditorInterface" ) );
Q_ASSERT( editor ); // This should not fail!
editor->setRegExp( expr->text() );
editorDialog->exec();
expr->setText( editor->regExp() );
}
}
Line 140;91 : KRegExpEditorInterface *editor =
static_cast<KRegExpEditorInterface *>( editorDialog->tqt_cast(
"KRegExpEditorInterface" ) );
What do I need to do to get make happy with the casts being done here? Can I
patch something? somewhere. You guys have a good one, I'm hitting the hay...
--
David C. Rankin, J.D.,P.E.
[View Less]
Archers,
As of tonight, I have all major packages that were previously building from
svn now building R14 from GIT :) Package list includes:
hal 0.5.14-8 [installed]
hal-info 0.20091130-1 [installed]
libutempter 1.1.5-3 [installed]
tde-arts 3513_tqt-1 [installed]
tde-dbus-tqt 3513_tqt-1 [installed]
tde-dbus-tqt-1 3513_tqt-1 [installed]
tde-libart-lgpl 3513_tqt-1 [installed]
tde-libcaldav 0.6.2_tqt-1 [installed]
tde-libcarddav 0.6.2_tqt-1 [installed]
tde-tdebase 3513_tqt-2 [installed]
tde-…
[View More]tdegraphics 3513_tqt-1 [installed]
tde-tdelibs 3513_tqt-1 [installed]
tde-tdevelop 3513_tqt-1 [installed]
tde-tdewebdev 3513_tqt-1 [installed]
tde-tqca-tls 3513_tqt-1 [installed]
tde-tqt3 3.8.8.d_git-1 [installed]
tde-tqtinterface 3513_tqt-9 [installed]
They work well too!
--
David C. Rankin, J.D.,P.E.
[View Less]
All,
Does anyone know how we can currently assign a short-cut key in kate/kwrite to:
Tools > Highlighting > Scripts > Bash
(alt+t, h, r, b -- isn't what I was thinking)
Or associate any of the other highlighting files with a short-cut? If there is
no way to do that, then it would be worth putting on the enhancement list.
Kwrite isn't that big of deal, but there are numerous times in kate where I will
have 10-20 files open that I would like to set with a syntax file without …
[View More]having
to mouse through Tools > Highlighting > Scripts > Bash that many times.
We could either have a key that popped open the Tools > Highlighting menu and
gave the user the ability to scroll and select. Or, my preference, would be to
provide a configuration option under highlighting that would be a "Quick List"
that allowed the user to configure his "Top 10" syntax files that would pop up
with a shortcut and allow the user to select from the list of 10.
It would need to be a katepart plugin to be available to both kate/kwrite, but
it shouldn't be that difficult to do.
Worth an enhancement request? There are already shortcut options for just
about everything in kate, just not syntax...
--
David C. Rankin, J.D.,P.E.
[View Less]