Message: previous - next
Month: December 2011

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

From: "Timothy Pearson" <kb9vqf@...>
Date: Sun, 18 Dec 2011 01:57:34 -0600
> 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
> dependencies/dbus-1-tqt
> dependencies/dbus-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.

The others are required for specific TDE modules/applications only--for
example, there is avahi support in kdebase, and knetworkmanager needs dbus
bindings.  So while modules other than tqtinterface and arts are
technically dependencies for certain modules, they are not global
dependencies required for *all* TDE modules.

> 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.

In the CMakeLists.txt file (usually found in the source directory of the
failing library/application) look for the lines that start with LINK. 
Tack " X11" (without the quotes) onto the end of those lines and you
should be set.  Also, please be sure to let us know which files needed
this treatment in a bug report!

> 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)

AFAIK this is the correct solution for handling non-standard system
library locations.