Date: Sat, 2 Nov 2019 23:41:51 +0100 From: Peter TKATCHENKO <peter@flytrace.com> To: gnome@FreeBSD.org Subject: FreeBSD Port: devel/meson Message-ID: <893B2CC5-6804-4D09-ABF7-C8BDF30AF2C7@flytrace.com>
next in thread | raw e-mail | index | archive | help
Hello, It seems that Meson does not respect FreeBSD path for pkg-config files = (*.pc). I found this PR: https://github.com/mesonbuild/meson/pull/4410 = <https://github.com/mesonbuild/meson/pull/4410>; that is still not = merged. Actually the workaround is in place for the ports system: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 = <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067>=20 Unfortunately, the workaround is not effective for manually installed = software. So, for any library, built with Meson, pkg-config files go to = the incorrect directory and cannot be found by pkg-config. This is = really confused for end-users. Would it be possible to fix the problem at Meson level?=20 It looks that the most simple way is adding to Meson a possibility to = force a pkg-config directory at the same way like it is doing for other = directories (for example, --libexecdir) - add a command-line parameter = --pkgconfigdir or something like this.=20 Another way could be patching Meson at the ports level and force the = correct directory here (I saw that some patches are already present in = the port). Right now a large project is migrating to Meson build system (EFL 1.23), = so everyone who wants to test it on FreeBSD is penalised by the problem = of pc files. Evidently, EFL developers suppose that the problem should = be fixed on Meson level https://phab.enlightenment.org/T8360 = <https://phab.enlightenment.org/T8360>=20 Could you, please, take attention to this problem? Best regards, Peter=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?893B2CC5-6804-4D09-ABF7-C8BDF30AF2C7>