trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2012

Re: [trinity-devel] Trying to fix bug #1170 (Kima FTBFS)

From: "Darrell Anderson" <darrella@...>
Date: Tue, 04 Dec 2012 14:51:04 -0600
>I am trying to fix the bug (#1170) where kima fails to build.
>However, I can not seem to get cmake to build the kicker applet. Is
>it possible to get the build scripts for it,, so that I can make my
>adjustments and see if they work.

As Slavek mentioned, kima has not yet been ported to cmake. Here 
are my basic configuration options:

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
  --prefix=${PREFIX} \
  --sysconfdir=${SYSCONFDIR} \
  --libdir=${LIBDIR} \
  --mandir=${MANDIR} \
  --with-qt-dir=${QTDIR} \
  --with-qt-includes=${QT_INCLUDE_DIR} \
  --with-qt-libraries=${QT_LIB_DIR} \
  --enable-gcc-hidden-visibility \
  $DEBUG_AUTOTOOL_OPT || exit 1

I seem to recall some list discussions about the problem. Possibly 
check the list archives:

http://trinity-devel.pearsoncomputing.net/

Note that kima builds without incident on systems that have HAL. 
The challenge is building kima on newer systems that don't have 
HAL. Resolving the bug report requires using the new Trinity TDEHW 
libs. That means building tdebase appropriately:

-DWITH_HAL=OFF
-DWITH_TDEHWLIB=ON

And of course ensuring that HAL is not installed on the build 
system. :)

Darrell