10 Mar
2012
10 Mar
'12
1:32 p.m.
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 -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.
10 Mar
10 Mar
10:38 p.m.
New subject: [trinity-devel] tdepim : build Failure: TQDialog' has no member named 'tqt_cast'
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:
Oh, man, (yawn) that's so yesterday. :)
Update to the latest GIT. That was one of the errors I had temporarily patched and
yesterday Tim fixed permanently after the recent tqt ABI tweaking.
Last night before going to bed I rsynced my local repository and started a full build
run.
This morning all is well again.
Darrell
10:58 p.m.
New subject: [trinity-devel] tdepim : build Failure: TQDialog' has no member named 'tqt_cast'
On 03/10/2012 12:38 PM, Darrell Anderson wrote:
Oh, man, (yawn) that's so yesterday. :)
Nothing like shooting at a moving target to hone your skills!
BTW, I went through your build script and -- man, that's not something you
through together in the past couple of days :) It will take a while to digest it
all with the difference between arch/slack build systems, but I was totally
impressed.
--
David C. Rankin, J.D.,P.E.
11:17 p.m.
New subject: [trinity-devel] tdepim : build Failure: TQDialog' has no member named 'tqt_cast'
BTW, I went through your build script and -- man,
that's not
something you through together in the past couple of days :) It will take
a while to digest it all with the difference between arch/slack build systems,
but I was totally impressed.
Thanks. :) Yes, the build scripts and environment evolved over two years.
Originally I only supported building KDE3, which was no longer being supported in
Slackware. Later I added TDE to the same setup. I could build KDE3 or TDE from those
scripts. I have those scripts and build tree through a different web page.
My current setup only supports TDE. I probably could reduce more overhead in my master
options template now that I no longer am building KDE3 in my new environment. Possibly
after R14 I'll look at additional streamlining.
In other words, if you see something that seems wasted, unused, or like cruft, you
probably are correct but now know how things got that way. But that is how most software
projects grow and evolve, n'est pas? :)
I'm not a computer science major. I'm just a person who is stubborn and works hard
at getting to a solution. There are better, slicker, and more optimized ways of doing
things. I adapt as I learn, but what I have works well.
I always want to learn but sometimes the goal is the solution and learning has to be a
side benefit. That is how I approach many of the bug reports these days. That is,
"let's get things resolved." Learning along the way is good but not my
primary goal for bug reports.
In the early days of my project participation I caused Tim grief asking him to adapt
things to build and work in Slackware. I think the project is the better for that, but I
still cause him grief. :)
Darrell
4789
days inactive
4789
days old
3 comments
2 participants
participants (2)
-
Darrell Anderson -
David C. Rankin