> > A while ago we had a discussion about building k3b. The
> configuration output declared not being able to find the
> dbus headers.
> 
> Yes, I think I posted that or was involved in the
> discussion. Why can't we make k3b find the dbus headers if we keep them in /opt/trinity?
> Couldn't we just edit the CMake files ConfigureChecks.cmake checks and have them
> check in the normal prefixes? /opt/trinity, /opt/tde, /usr?  Or why not
> have the cmake files create and source a file similar to /etc/profile.d/trinity.sh.? You
> could use a check to test for the actual trinity.sh, use it if present, else
> use one based on the chosen prefix at the start of the build with tqt3?

I have since learned that the Trinity dbus-tqt package is a full dbus package replacement (there are only a few files in the package). The reason for the additional files in /usr/include/dbus-1.0/dbus is from other dbus related packages, such as dbus-glib and dbus-python.

Installing the modified dbus-tqt package to /usr bothers me because I don't know the effect on other distro packages that built against the original dbus package, which is being replaced by the tqt layer. Those distro packages know nothing about the tqt layer.

The alternative is installing dbus-tqt to any place other than /usr means various Trinity packages don't build correctly.

I agree the build configuration and make files should be modified to use the Trinity version of the dbus headers so the stock distro system remains unaffected. Only Trinity packages need to adjust to the modified dbus headers.

I don't know how to make those modifications.

With kmplayer I found a work-around of using --with-extra-includes. That work-around fails with k3b.

Perhaps installing dbus-tqt to /usr has no effect on distro packages, but nobody answers these questions.

Darrell