On 01/28/2014 11:28 AM, Darrell Anderson wrote:
> I always thought the answer is either. When tdebindings is built 
> and installed with libsmoke support, then libtqt-perl is not 
> supposed to build libsmoke. When tdebindings is not installed or 
> built without libsmoke support, then libtqt-perl is supposed to 
> build its own libsmoke.
> 
> I always build tdebindings before libtqt-perl.

Let's start with the last part first:

>
> But what do I know?

--> A lot!, that's why we are renaming the 'trinity-devel' list to the
'darrell-anderson' list...

  Now on to the more pressing matter -- how to control:

if libsmoke from A, then
  no libsmoke from B
elif libsmoke from B, then
  no libsmoke from A
fi

  Is this purely a packaging matter, of should there be some TDE logic that does
this in the autotool/automake setup.

  Right now libtqt-perl is a prime example of the hell we will find ourselves in
when automake 2 arrives. It does not build with automake 1.14 without
significant hacks. Slavek has taken an initial patch of the problem and created
an update to libtqt-perl and it looks like he has set libsmoke to build only in
tdebinding. See:

http://bugs.pearsoncomputing.net/show_bug.cgi?id=1875#c5

  So that it the way we will go.

-- 
David C. Rankin, J.D.,P.E.