Le 08/12/2011 05:42, Bruce Dubbs a écrit : > There are two issues. Qt3 and qt4 have completely different libraries, > but their build tools, moc and qmake, have the same names. The easy > solution there is to put the desired executables first in PATH. After > the build is complete, then this is not an issue. Qt4 does not need any > environment variables set if the PATH is right.
Yes, there's no problem with Qt3 and Qt4 side by side. And Trinity uses its own version of Qt3 (3.3.8d), with a library (tqtinterface) which is, AFAIK, a kind of wrapper to qt functions. > I don't know if any KDE4 and Trinity libraries have a name conflict. I > would suspect that some executable names, e.g. konsole, would conflict. > Again that is easily solved solved with the right PATH for > executables, but libraries may be an issue. About libraries, I didn't see any problems of that kind. With executables, trinity solves the conflict at startup, by inserting /opt/trinity/bin at the beginning of the path, (startkde script). > I don't know how KDEHOME is used. By default, if not defined in the environment, KDEHOME is ~/.kde. That's where there is a little problem. Since I didn't intend to install KDE4 in LFS, I didn't see until now that this problem isn't solved in BLFS either. If you install KDE3 and KDE4 at the same time, without taking care of KDEHOME, they will share the same folder for their settings, and that will produce a lot of strange bugs. Trinity defines KDEHOME as ~/.trinity. As long as you don't run KDE4 apps inside of trinity, that's OK. But to be able to use KDE4 apps and avoid bugs, the solution is to patch trinity to use TDEHOME instead of KDEHOME (or to patch KDE4 to use KDE4HOME instead). -- Laurent Dard -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
