Message: previous - next
Month: July 2012

Re: [trinity-devel] What causes "checking for tde-config... not found" failures?

From: "David C. Rankin" <drankinatty@...>
Date: Sat, 28 Jul 2012 15:40:35 -0500
On 07/28/2012 01:05 PM, Darrell Anderson wrote:
> kde-config was renamed to tde-config after 3.5.13:
> The solution then is the configure/make files should be looking for
> kde-config, unless slavek backported the name change to
> Darrell

Thank you Darrell!

  I knew we nicked our own Achilles tendon when we went on the massive k->t
rename. For graphics, etc. that are user seen it was a needed part of the normal
progression of the desktop, but for unseen checks and items that do not conflict
with kde4, we really need to think ahead and make sure we are not shooting
ourselves in the foot. From a build system standpoint, accept for upstream
changes, we should be able to build TDE 3.5.12, 3.5.13 and R14 without our
naming system interjecting incompatibilities into the build.

  I'll play with this and see if I can't come up with and conditional or
pre-processor type check on the version number to use the right kde-config or
tde-config, because it just seems like something like that should be simple.
I'll have to look, because I can't explain why 70% of the sru branch built and
30% failed based on this tde-config/kde-config issue. But I'm completely
encouraged by how well 3.5.13 built.

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