I also tried to compile with tqt3, but it doesn't compile neither.
make[4]: Entering directory
`/home/midenok/src/kde/tqt3/tools/designer/designer'
/home/midenok/src/kde/tqt3/bin/uic -L /home/midenok/src/kde/tqt3/plugins
customwidgeteditor.ui -i customwidgeteditor.h -o customwidgeteditor.cpp
make[4]: *** [customwidgeteditor.cpp] Segmentation fault
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff14f893c in ?? () from /opt/kde3/lib/libkabc.so.1
(gdb)
(gdb) bt
#0 0x00007ffff14f893c in ?? () from /opt/kde3/lib/libkabc.so.1
#1 0x00007ffff752abc2 in TQApplication::~TQApplication
(this=0x7fffffff8520, __in_chrg=<value optimized out>) at
kernel/qapplication.cpp:1038
#2 0x000000000040db67 in main (argc=8, argv=0x7fffffff8bd8) at main.cpp:74
Can you guess why this happening?
I know it isn't ready but I would like to try to build the git
version from scratch (on LFS).
I have already installed those prerequisites:
xorg7 (without xrx compiz grandr mkcfm xcompmgr xphelloworld libAppleWM
libWindowsWM libpthread-stubs)
XCB (with libpthread-stubs)
dbus-1.5.6
qt-3.3.8d (patched for libpng-1.5.4)
qt-4.7.4
dbus-1-qt3-0.9
dbus-python-0.84.0
libart-lgpl-2.3.21 (patched)
From what I see in git, I'm going to build:
tqt3
tqtinterface
arts
tdelibs
dbus-tqt
dbus-1-tqt
python-tqt
tdebase
Here is my questions:
- Is it the right order?
- Am I missing something?
- arts: how to include jack support?
-ljack? -DWITH_JACK? -DHAVE_LIBJACK? export HAVE_LIBJACK?
nothing of these worked last time I tried, but without cmake I had:
$ ldd /opt/trinity/lib64/libartsflow.so.1.0.0
> libjack.so.0 => /usr/lib64/../lib64/libjack.so.0 (0x00007f9b7cc18000)
Is it worth a bug report?
- tqt3: does it completely replace qt3?
- dbus-1-tqt: does it replace dbus-1-qt3-0.9?
- python-tqt: does it replace dbus-python-0.84.0?
--
Laurent Dard
Hey guys,
I spend a lot of time working with Bugzilla so I did some research about a
frontend since KBugBuster is busted.
it's called Deskzilla and works well with Trinity's Bugzilla tracker.
http://almworks.com/deskzilla/overview.html
it's quite useful!
Thought maybe someone would be interested
Calvin Morrison
Hello,
I'm curious if tqt have any future, we really want to run trinity over Qt > 3?
From a developer perspective tqt layer is pretty sux, every time I need to
remember to use T prefix, namespace is polluted with hundreds of useless
macros, a lot strings have been damaged by automated migration tools, .ui
files cannot be opened directly by designer, etc etc. Also, I'm pretty sure
that many bugs have been introduced in process (I remember that few times I
waste hours to debug strange behaviour because tqt). Even now I notice
in .xsession-errors errors like "WARNING: DCOPReply<>: cast to 'TQCString'
error".
We need to handle all these problems, with no real benefit (ar least from my
perspective).
--
Serghei
In KDE3 the task bar icons stretch from the top of the task bar to the bottom. There is no space above or below the icons. That is, the icons fully fill the task bar from top to bottom.
In TDE the icons do not fully fill the task bar. There is a thin space above and below the task bar icons.
Are the icon heights configurable in TDE?
I'm referring to the task bar only and not the quick launch or system tray icons.
Darrell
Or: "Lions and tigers and ebuilds, oh my!"
Yes, I know there are no official packages for Gentoo yet. I decided to see
if I could do something useful by installing what unofficial ones were available
and probing for bugs, and possibly rolling a few ebuilds of my own for the
packages that haven't gotten any love yet. I used non7top's GitHub fork of
Serghei's ebuild repository (at the time I started, the contents of the two were
identical, actually) and did manage to get kdebase installed after two ebuild-
related hiccups.
After that, things started to get complicated, and I ran into a variety of
problems. Unfortunately, I haven't been able to decide whether some of
them are Trinity bugs, ebuild bugs, or just Gentoo quirks, so I don't know
where to file them and need help with the triage.
__________________
Problem #1: Unset environment variables
When I first booted Trinity, the desktop *appeared* to come up exactly as
it should, but most applications would not start, the main menu was nearly
empty, and kcontrol had no settings available. After some mucking around,
I discovered that there was no mention of the Trinity bin directory in my
PATH, and then found that Gentoo set PATH, ROOTPATH, LDPATH, and
XDG_DATA_DIRS inside a distro-specific part of starkde (for KDE 3.5.10,
that is), so I copy-and-pasted those into the startup file provided. (I know
there are some setters in the Trinity startup script. They didn't work,
possibly because of Problem #4.)
Unfortunately, that didn't fix things--I also needed to set LD_LIBRARY_PATH
for programs (including konsole) to start properly, and XDG_DATA_HOME,
XDG_CONFIG_HOME, and/or XDG_CONFIG_DIRS (I never tried setting
them individually, so I can't narrow it down) to get a working menu and kcontrol.
I don't know what changed between KDE 3.5.10 and Trinity 3.5.13 to make
the setting of those additional environment variables necessary, so I'm not
sure who owns the second half of the bug.
__________________
Problem #2: Autotools packages and ebuilds
I did manage to write some successful ebuilds (I have most of kdegraphics and
kdeartwork working, if anyone wants ebuilds for those, plus kdebase-meta and a
variant ksmserver ebuild with a hal useflag), but only for packages that have been
ported to CMake. The autotools packages Will Not Work, no matter how I mangle
the KDE 3.5.10 ebuilds (rewriting from scratch is not an option, IMAO--the old
kde-meta eclass contains several hundred lines of bash script, and spending more
than minimal time on a build system that's going away is wasted effort).
After a lot of playing around with kdetoys, I was able to figure out that I was
running into two problems: a minor change in the tarball structure (not a bug, solved
by a 1-line fix), and a set of missing build/config files. The kdetoys-3.5.10 tarball
contains a bunch of files at the top level that are missing from its 3.5.13 equivalent:
configure.in, acinclude.m4, aclocal.m4, and several other config* and Makefile*
files. When I copied these files from the old to the new package, the ebuild got
as far as actually configuring/building the package (and, naturally, failed, because
the old buildscripts didn't know about TQT, but it was the first iteration that didn't
bail out while trying to find the build directory or run eautoreconf/aclocal).
I know next to nothing about autotools, so I don't know if those files were
removed for a reason. Maybe someone who knows more about autotools
and ebuilds could do something without them; I just know that *I* can't.
Another thing is that I couldn't seem to get the --without-arts switch to work,
but with the ebuilds so messed up to begin with it's difficult to tell whether
that's meaningful.
__________________
Problem #3: CMake failures
Ebuilds for two subapplications of kdeutils that were included in the stuff I took from
GitHub failed to build, complaining that they weren't able to find tqt.h (one of them would
have been Ark). I don't know whether this is an ebuild or a CMake bug.
__________________
Problem #4: startkde/starttrinity and minimal or unusual builds
While I was wrestling with Problem #1 above, I had occasion to examine both
the new and the old startup scripts in detail, and there were some things in the
new one that drew my attention. However, I'm not sure they really qualify as bugs:
if [ -d /opt/trinity/games ]; then
That, and the lines that follow it, might work fine if Trinity is installed into
/opt/trinity/, but Gentoo's practice is to install most software into /usr/.
Something like:
if [ -d ${KDEDIR}/games ]; then
might be more portable.
# Make sure a default wallpaper is set.
if [ ! -e $kdehome/share/config/kdesktoprc ]; then
# With Trinity this file should exist, but test first.
if [ -r /usr/share/wallpapers/isadora.png.desktop ]; then
cat >$kdehome/share/config/kdesktoprc <<EOF
[Desktop0]
Wallpaper=isadora.png
WallpaperMode=Scaled
EOF
fi
fi
Not having a wallpaper set is harmless--these lines seem to add complexity to
the script for no good reason (and I don't have a /usr/share/wallpapers, either--
isadora.png is in /usr/kde/3.5/share/wallpapers--so this code isn't portable).
Perhaps it belongs in a distro-specific patch?
# Configuration of the gtk_qt_engine if not already set.
[...]
Trinity will run quite happily without gtk-qt-engine installed, so a test needs
to be made for that (at minimum--I'd relegate this to "distro-specific" too).
# Remove moodin cache if we have a new wallpaper installed, jriddell. Distro-specific.
if [ -d $kdehome/share/apps/ksplash/cache/Moodin/kubuntu ]; then
if [ /usr/share/wallpapers/kubuntu-wallpaper.png -nt $kdehome/share/apps/ksplash/cache/Moodin/kubuntu/ ]; then
rm -rf $kdehome/share/apps/ksplash/cache/Moodin/kubuntu/
fi
fi
This says right out that it's a Kubuntu patch. It doesn't belong in vanilla Trinity.
$KDEDIR/bin/artsshell -q terminate
Arts is another optional component that Trinity can operate without, so it shouldn't
be shut down without testing to see if it's there. Maybe:
if test -e $KDEDIR/bin/artsshell ; then artsshell -q terminate ; fi
(The prelinking stuff isn't in my old startup script either, but I suspect that Gentoo may
have removed it.)
__________________
I think that's everything. The other (minor) bugs I ran into I'm fairly sure I know where
to file.
While searching some info on the net about porting projects from
autotools to cmake i have found this:
http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide#CMake
Apparentely they have script that converts automatically .am files to
cmake files. I've run it on several not-yet-ported-to-cmake trinity
components, and it generated nearly whole CMake files structure. Yet
it doesn't generate config.h.cmake file which is needed (without it
compilation simply don't happen). I've asked for help on kde-devel irc
channel, but without any success (maybe I'll ask later).
Whole point is, maybe we could adapt this to generate our cmake files,
thus speeding whole porting to cmake?
Several days ago when I started my koffice nightmare, I submitted bug report 721 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=721).
For the poppler warning messages I ran across a patch from Francois. I updated the bug report with a link to the patch already in GIT.
Today I ran across the likely cause to the ruby messages: the configure scripts do not support ruby 1.9.x (https://gist.github.com/1414497).
I started a patch but still receive the warning message. I'm missing something else but don't know what.
Here is the patch:
=======================================
diff -urN koffice/configure.in koffice.new/configure.in
--- koffice/configure.in 2011-08-21 18:30:53.000000000 -0500
+++ koffice.new/configure.in 2011-12-08 12:56:01.215427952 -0600
@@ -1539,14 +1539,20 @@
# Check for Ruby
if test "x$compile_kross" = "xyes" ; then
- AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18], ruby)
+ AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18 ruby1.9 ruby19], ruby)
if test -n "$RUBY"; then
AC_MSG_CHECKING(for Ruby dirs)
RUBY_ARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"archdir"@:>@)'`
RUBY_SITEARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitearchdir"@:>@)'`
RUBY_SITEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitelibdir"@:>@)'`
- RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'`
+ if test -n "$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'"; then
+ # Ruby 1.9
+ RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'`
+ else
+ # not Ruby 1.9
+ RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'`
+ fi
RUBY_LIBDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"libdir"@:>@)'`
RUBY_LIBRUBYARG=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"LIBRUBYARG_SHARED"@:>@)'`
RUBY_ENABLESHARED=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"ENABLE_SHARED"@:>@)'`
@@ -1602,7 +1608,7 @@
#include <version.h>
],[
-#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR == 8 && RUBY_VERSION_TEENY <= 1)
+#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR >= 8 && RUBY_VERSION_TEENY <= 1)
#error "need at least ruby 1.8.2\n"
#endif
diff -urN koffice/lib/kross/configure.in.in koffice.new/lib/kross/configure.in.in
--- koffice/lib/kross/configure.in.in 2010-08-11 22:16:27.000000000 -0500
+++ koffice.new/lib/kross/configure.in.in 2011-12-08 12:56:45.787428312 -0600
@@ -21,14 +21,20 @@
# Check for Ruby
if test "x$compile_kross" = "xyes" ; then
- AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18], ruby)
+ AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18 ruby1.9 ruby19], ruby)
if test -n "$RUBY"; then
AC_MSG_CHECKING(for Ruby dirs)
RUBY_ARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"archdir"@:>@)'`
RUBY_SITEARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitearchdir"@:>@)'`
RUBY_SITEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitelibdir"@:>@)'`
- RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'`
+ if test -n "$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'"; then
+ # Ruby 1.9
+ RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'`
+ else
+ # not Ruby 1.9
+ RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'`
+ fi
RUBY_LIBDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"libdir"@:>@)'`
RUBY_LIBRUBYARG=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"LIBRUBYARG_SHARED"@:>@)'`
RUBY_ENABLESHARED=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"ENABLE_SHARED"@:>@)'`
@@ -84,7 +90,7 @@
#include <version.h>
],[
-#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR == 8 && RUBY_VERSION_TEENY <= 1)
+#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR >= 8 && RUBY_VERSION_TEENY <= 1)
#error "need at least ruby 1.8.2\n"
#endif
=======================================
If we get this resolved the patch will be available to close the bug report. :)
Thanks for any help.
Darrell
I'm trying to build some trinity components manually, since no
binaries, nor build scrips (PKGBUILD) are available for my distro
(arch), and I wonder, why when I try to compile something using
autotools (because obviously it hasn't been ported to cmake yet) it
keeps me asking for Qt >=4.3 and <5.0.
Besides I looked a little at files present in the admin dir and I
found that some of the paths for libraries are hardcoded and point to
(example) /usr/share/kde3 or /usr/share/qt.
Another thing, shouldn't automake files be removed form components
that have been ported to CMake. Since autotools-based compiling aren't
really supported for those...
And I'd be grateful of someone could write a little about how to port
trinity components to cmake. I'd like to help, I get the main idea,
but I don't know where too look for dependencies and stuff like that.
