Btw, anybody done QT6 build of ftinspect lately?When I was writing the
makefile, I had to install some qt5*-devel packages. I did some qt3/qt4 stuff a
long time ago, so I kept those, but uninstalled most of qt5-dev stuff when I
see qt6 being installed as part of half-yearly upgrade. I am on gnome, so kde
stuff is really around for occasional curiosity. I just checked kde is still
qt5... and only about 2 GUI applications I use depends on QT6 libraries.
Anyway, I see some QT6 compatibility code in ftinspect, but they seem to have
gotten bit-rotten / still WIP?
On Monday, 17 July 2023 at 00:22:05 BST, Hugh McMaster
<hugh.mcmas...@outlook.com> wrote:
On Fri, 14 Jul 2023 at 00:49, suzuki toshiya wrote:
> The pkg-config interface should take care of everything easily. Debian and
> Ubuntu have the relevant qt5 pkg-config files. Other distributions should too.
Does pkg-config give the information for the pathname of moc?
(the original question by Hin-Tak was asking about the
appropriate path to use moc command)
In my understanding, pkg-config is primarily designed to
provide the information to compile & link the libraries,
not designed to provide the information about the binary
executable commands.
Extra information beyond the standard prefix, sysconfdir, libdir etc. is
package dependent.
In this case, Qt5Core.pc has a variable that provides the path to a directory
containing binaries such as moc.
