Tim, all,
As expressed in my email to Tim, my goal is to build trinity (from svn) for
Arch Linux to replace the old Chakra project kdemod3. (which is no longer
supported or available) I'm very proficient in Linux, but I SUCK with cmake. It
might as well be Greek. I've been through:
http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild
and I've stumbled across the linuxquestions.org thread stating you must remove
all existing kde3 installs before building trinity. (Tim this seems to answer my
question whether I can do a parallel install of trinity in /opt/trinity and keep
my existing /opt/kde) So do I really have to nuke my existing kde3 install prior
to building trinity? (assuming yes from the following link)
http://www.linuxquestions.org/questions/slackware-14/trinity-kde-3-5-12-a-8…
This is where I hit my first roadblock.
(Issue #1) Arch Linux provides python2-sip and pyqt3, but not pykde. I've
downloaded and written an Arch PKGBUILD script to build the PyKDE-3.16.7 package
for Arch. (see: https://bbs.archlinux.org/viewtopic.php?pid=881478#p881478)
However building pykde requires dcopobject.h. Trinity provides:
trinity/kdebindings/dcopc/dcopobject.h
trinity/kdelibs/dcop/dcopobject.h
(of which the kdelibs dcopobject.h looks correct) However, to build pykde, I
have to provide reference to the installed kde3 base (-k /opt/kde) to get it to
build:
python2 configure.py \
-d /usr/lib/python2.7/site-packages \
-v /usr/share/sip -k /opt/kde
which builds fine, but the linuxquestion.org thread says if you build against
the existing 3.5.10 dcopobject.h you will have build failures later on. So
what's the trick to get pykde to compile using the dcopobject.h from svn?
(Issue #2) How in the heck to I choose QT3 to get tqtinterface to build? I know
this is a simple switch issue or environment issue, but I've googled and have
just managed to broaden my confusion. This is my cmake shortcoming. When I
attempt the build, I get:
11:49 archangel:/tmp/dependencies/tqtinterface> cmake ./
CMake Error at cmake/modules/TDEMacros.cmake:20 (message):
#################################################
You must select a Qt version
#################################################
Call Stack (most recent call first):
CMakeLists.txt:46 (tde_message_fatal)
-- Configuring incomplete, errors occurred!
The error is obvious, I need to tell it which Qt version to use, but obviously
I'm too stupid to figure out where or how. Can somebody help a brother out here
and help lift the veil of confusion I'm suffering from here?
Also, I've started a build script to automate the trinity build after I get the
dependencies built. Basically to automate the libtool.m4.in, ltmain.sh and make
-f setup and then provide correct ./configure options that --enable-closure when
required based on the module name. The the plan is simply to build trinity in
the order specified in the HowToBuild from a static list or array. Before I
reinvent the wheel, does anything like this exist? Also, the wiki is a bit
sparse. If anyone has more detailed notes squirreled away on the build process
or how to setup a better build environment/chroot/whatever, if you will make
that information available, I'll commit to adding it to the wiki (with proper
attribution of course)
For anyone interested, I have started the build script and have it functional up
to the point of adding the ordered list to build each module. (currently it is
just a concept that outputs what it will do without actually doing anything).
Basic use is:
sh bldtrinity.sh [ path/to/your/trinitysvn path/to/libtool.m4 path/to/ltmain.sh ]
my defaults [Arch locations]:
trindir=${1:-/home/david/arch/pkg/trinity}
syslibtool=${2:-/usr/share/aclocal/libtool.m4}
sysltmain=${3:-/usr/share/libtool/config/ltmain.sh}
The beginnings of the script are at:
http://www.3111skyline.com/dl/dt/trinity/scr/bldtrinity.sh
I welcome any suggestions or comments. Thanks. I look forward to this project.
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
Hi all!
My name is Bartlomiej i'm from PLD Linux distro.
I have problems with tqt compilation/instalation.
Here is log configure/compile log: http://pld.pastebin.com/ja58wz3c
Problem is because there is no tqt.so.x.y.z files only symlinks
[cactus@carme-pld qtinterface]$ ls -l .libs/libtqt.*
lrwxrwxrwx 1 cactus users 12 01-03 11:05 .libs/libtqt.la -> ../libtqt.la
-rw-r--r-- 1 cactus users 1515 01-03 11:05 .libs/libtqt.lai
lrwxrwxrwx 1 cactus users 15 01-03 11:05 .libs/libtqt.so -> libtqt.so.4.2.0
lrwxrwxrwx 1 cactus users 15 01-03 11:05 .libs/libtqt.so.4 -> libtqt.so.4.2.0
[cactus@carme-pld qtinterface]$
when building --with-static it produces libtqt.a archive.
any hint?
Best regards
Bartlomiej Zimon
KDE-Trinity 3.5.12 on Debian Squeeze, running the Trinity desktop.
In Gwenview, I can open and view .tiff files. If I rotate, or modify, the image
and try to save, I get a ( paraphrase) can not write tiff format error. Is this a
tiff support issue in KDE3 or something else?
--
Peace,
Greg
I am using Slackware 13.1 and wondering if anyone has had success compiling
trinity in this environment. I have used a chroot environment with no KDE
installed at all and also a stripped Slackware (slax) with no KDE and qt3.
If using the svn and build scripts i get 'no uic-tqt' errors all the time
and nothing gets compiled. If compiling manually i get as far as compiling
tqtinterface, arts & kdelibs. I am having no luck compiling kdebase though.
So my question is if anyone has had success compiling under slackware 13+
please let me know the best way to compile.
All,
The Trinity Desktop Environment development team is attempting to find out
which distributions and version Trinity is currently installed and used
on, so that we may focus our efforts on improving compatibility with those
distributions.
We politely ask that you add your distribution to the informal poll on the
Wiki here:
http://trinity.pearsoncomputing.net/wiki/bin/view/Community/UsageSurvey2011
If your distribution is already listed, please increment the number of
users for that distribution by one (1). If more than one individual in
your household is using that distribution, please increment the number of
users by the number of users in your household. Also, if you use more
than one distribution, please increment the number of users appropriately
for each distribution in use.
The results of this poll will also help the Trinity development team
decide which distributions are too old or little-used to be supported in
future Trinity release, so please cast your vote if you want to see your
distribution supported in the future.
Thank you,
Timothy Pearson
Trinity Desktop Environment Development Team
Hi,
Anybody knows how to disable smooth scroll in konqueror and kmail?
Is useless and very annoying, I propose to disable smooth scrolling by
default.
--
Serghei
I have spent some time developing a Squeeze live-cd with Trinity. Why?
Because there is nothing out there in the mainstream that I like and I
have seen no Squeeze/Trinity live-cd elsewhere yet. It is named Exe
Linux as I live beside the Exe Estuary in Devon, England.
It might be a good starting point or demonstration for anyone who is
interested but is unsure of running Trinity on Squeeze.
The result has (to the best of my knowledge) strictly GPL software. Some
custom themes, configurations and scripts are included but are
debianized, i.e. they can be removed/replaced by apt (for example extra
live-config scripts to support Trinity autologin and locale/language)
and should not conflict with Squeeze core system components
The live cd has an optional integrated installer (hacked remastersys)
for HD and a custom CLI script for USB persistent pendrive.
It is built "from scratch" using custom scripts, debbootstrap and GNU
tools (not live-helper nor remastersys) and is not a "remaster" of
anything else. The build scripts are included in the live-cd but are
experimental and, misused, could trash a running system. If you want to
try a remaster better use remastersys (and please don't request support
from remastersys forums because a hacked version is used).
Three locales/languages are built-in (US, GB and ES) No more fit the CD
without removing one.
If there is any interest I would like to make this available to Trinity
users, perhaps later in the "community downloads" section.
In the meantime the current ISO (685MB) is available here (can paste
this in a terminal):
wget -c
"http://exe-linux.fastfishwebsolutions.com/trinity/exelinux_squeeze_trinity_…"
md5sum:
wget -c
"http://exe-linux.fastfishwebsolutions.com/trinity/md5sum_exelinux_squeeze_t…"
Disclaimer: This is *not* an official Trinity project. There are
probably some bugs. There is some scrappy and probably out-of-date
documentation. Use at your own risk.
> Hi,
> I have a few questions about the Trinity project status,(part of them
seem to have been partially discussed on the list):
> - Is Trinity endorsed in any way by the KDE project (except the share
> of sources repository)?
Not that I know of.
> - Are there original KDE3 developpers involved in Trinity development?
> If so, I'd really like to know if they do it because KDE4 broke too much
things (and/or they consider a desktop environment should not break
things this way)?
Only incidentally, in that I pull updates from the kdepim Enterprise
branch, which is still maintained by an original KDE3
developer/development team.
> - What are the long term perspectives about Trinity?
> Will Trinity become something different than KDE3 or it keep it as
> close as possible?
As close as possible in terms of look and feel, but new features will
still be added where they would improve the functionality of the desktop
environment (e.g. krandrtray). Users can always disable new features from
the control panel, as providing that option is a requirement for patch
submission.
> I mean, the move from KDE3 to KDE4 changed & broke a lots of things
> that I used to work with since 2004. I'd really like a desktop
> environment that doesn't change too much, that keeps its basis stable
(eg. themes can evolve, apps be improved, but keep it functionally the
same!).
> By the end, I really think it's a matter of "respect for users": if one
changes things like KDE4 did, what do we have to think about respect
they have (or don't have) for their users? OK KDE4 is beautiful, etc.
but it's deaply another desktop environment (also deeply slow in some
particular configurations such as konsole/nvidia ships), so why should I
continue to use KDE desktops? I almost think KDE4 should have change its
name to something else OR... KDE3 should have been officially
> maintained... or Trinity officially endorsed (is that the case?)!
KDE won't change its name, but KDE3 has changed its name to Trinity. So,
KDE3 == Trinity, KDE == KDE4, but KDE3 != KDE4.
> So, what's going on?
> Thank you,
> Nicolas
> PS: Do you have an idea about the approximate number of Trinity users?
It seems this list is always growing...
Not sure! I know we had 3000+ downloads of the Maverick Desktop LiveCD
from one mirror alone last month, but the actual user number may be much
higher.
Hope this helps!
Tim