trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2011

Re: [trinity-devel] Building kdeadmin

From: Bruce Dubbs <bruce.dubbs@...>
Date: Thu, 22 Dec 2011 12:12:31 -0600
L0ner sh4dou wrote:

> 1) Did you install TQtinterface in /usr? 

No, in /opt/trinity.

> I had the same error, and
> apparently autotools will refuse to detect it correctly if it's not
> installed in /usr.

> 2) Try specifying manually paths to Qt3 in your ./configure
> (--with-qt-dir= option if I remember correctly).

I already tried that.  It does not work for me.

> For building trinity, check out arch PKGBUILDs in our git tree. They
> are pretty much bash scripts with some variables used by pacman to
> create binary packages. What you need to look at is the build()
> function.

Is there a way to browse the git tree via a web interface?

After some more research, the following works for me:

---------
TRINITY_PREFIX=/opt/trinity

cp -v /usr/share/aclocal/libtool.m4       admin/libtool.m4.in
cp -v /usr/share/libtool/config/ltmain.sh admin/ltmain.sh

sed -i -e "s@/usr/include/tqt@$TRINITY_PREFIX/include/tqt@" \
           admin/acinclude.m4.in

make -f admin/Makefile.common

./configure --prefix=$TRINITY_PREFIX \
             --enable-closure         \
             --sysconfdir=/etc        \
             --localstatedir=/var     \
             --with-extra-libs=$TRINITY_PREFIX/lib

make
---------

admin/acinclude.m4.in hard codes /usr/include/tqt instead of getting it 
from tqt.pc, which is set up correctly on my system.  It also does not 
set up the Trinity libraries correctly, even though it could be 
determined from either the PATH or --prefix.

Note that I could not detect any effect for --sysconfdir or 
--localstatedir for kdeadmin.

   -- Bruce