trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

tdelibs kstandardirs - KDELIBSTUFF - can it be tied to $prefix?

From: "David C. Rankin" <drankinatty@...>
Date: Wed, 04 Apr 2012 19:08:54 -0500
All,

  Looking at the tdelibs/tdecore/kstandarddirs.cpp locations, I noticed the
KDELIBSTUFF is hard coded to /trinity /trinity/plugins for module and qtplugin
types. I've wondered why that wasn't /tde and /tde/plugins since it replaces
/kde /kde/plugins. Is there a way to pass an environment variable or something
similar to the file so that the following code:

TQString KStandardDirs::kde_default(const char *type) {
<snip>
    if (!strcmp(type, "lib"))
	return "lib" KDELIBSUFF "/";
    if (!strcmp(type, "module"))
	return "lib" KDELIBSUFF "/trinity/";
    if (!strcmp(type, "qtplugins"))
        return "lib" KDELIBSUFF "/trinity/plugins";
<snip>

could do something like:

TQString KStandardDirs::kde_default(const char *type) {
<snip>
    if (!strcmp(type, "lib"))
	return "lib" KDELIBSUFF "/";
    if (!strcmp(type, "module"))
	return "lib" KDELIBSUFF "/tde/";
    if (!strcmp(type, "qtplugins"))
        return "lib" KDELIBSUFF "/tde/plugins";
<snip>

  What I don't have a feel for is how the hard coded /trinity location trickles
through the rest of the code. If it is relied on by much of the rest of the
build, it isn't worth fixing, but hard coding the location seems like it could
lead to issues later. Just a stray thought.

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