Message: previous - next
Month: December 2011

Re: [trinity-devel] Adding Trinity to Linux From Scratch

From: Robert Xu <robxu9@...>
Date: Sun, 18 Dec 2011 02:58:58 -0500
On Dec 18, 2011, at 2:00, Bruce Dubbs <bruce.dubbs@...> wrote:

> I am starting to do the development/testing needed to add Trinity to Linux From Scratch, replacing KDE3.  Right now I have a couple of issues I'd like to get clarified.
> First, I notice in the dependencies directory, there are several packages:
> dependencies/arts
> dependencies/avahi-tqt
For any app that needs avahi
> dependencies/dbus-1-tqt
Substitute the Qt4 backport bus bindings with these for any app that needs it
> dependencies/dbus-tqt
Original dbus qt3 bindings ported to tqt
> dependencies/tqtinterface
> I have no problems with arts or tqtinterface but I don't see the other three mentioned anywhere.  Are these packages required for Trinity?  If so, at what point are they required?  We do have instructions already in LFS for D-Bus and avahi libraries.

Basically, if a kde3 package needed the qt3 one, they now need the tqt one.

> Second, I have had some problems building kdelibs.  There were no problems following the instructions for qt3, tqtinterface, or arts, but there were many places in building kdelibs where I had to edit a link.txt file and add -lX11.  I am fairly new at using cmake so I'd like to know if there is a way to add this automatically.
> My installation of xorg is a little non-standard because the files are in /opt/xorg, but there are appropriate symlinks at /usr/X11R6 and /usr/include/X11.  I didn't seem to have a problem with include files.
> It would also be useful to know how to set -L/opt/xorg/lib, but that is not critical because I can do essentially the same thing by export(ing) LIBRARY_PATH.
> I'll note that LFS has a policy of not using development versions of packages, so for now we need to be able to work with trinity-3.5.13.

There's also R14 coming out in 4 more months :P
I remember that I wanted to do BLFS for 3.5.12 (and bringing it up),
but the lower autoconf version seemed to be a problem. You'll realized
that we haven't fully converted to cmake :-/

> Thanks for your help.
>  -- Bruce Dubbs