freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: skeletal makefile for ftinspect (Re: Future of autotools)


From: Hin-Tak Leung
Subject: Re: skeletal makefile for ftinspect (Re: Future of autotools)
Date: Sun, 16 Jul 2023 23:49:48 +0000 (UTC)

Yes, the moc location on fedora 38 can be queried with:

pkg-config Qt5Core --variable=host_bins

If this works correctly on other systems, we should set 

MOC=`pkg-config Qt5Core --variable=host_bins`/moc

Or put PATH=${PATH}:`pkg-config Qt5Core --variable=host_bins` and MOC=moc ?

I am more inclined towards the former, few surprises.

On Monday, 17 July 2023 at 00:22:05 BST, Hugh McMaster <hugh.mcmaster@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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]