Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124221
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 4 Jul 2024 18:09:22 +0200
Message-ID: <CAAfnsFUuK1ncfqNiUCukTkFuG-LTgj8eqH9D51Tu-3hhba13SQ@mail.gmail.com>
Subject: [PHP-DEV] Support for pkg-config .pc files
To: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000522e49061c6e2c3f"
From: petk@php.net (Peter Kokot)

--000000000000522e49061c6e2c3f
Content-Type: text/plain; charset="UTF-8"

Hello,

There is another pull request in preparation that I'd like to squeeze in
the PHP-8.4 branch if it will possible to wrap it up until the feature
freeze milestone:
https://github.com/php/php-src/pull/13755

In short, pkg-config is *nix command line utility to query installed
libraries on the system:
https://en.wikipedia.org/wiki/Pkg-config
https://people.freedesktop.org/~dbn/pkg-config-guide.html

And pkgconf is a compatible maintained continuation/fork that many
distributions might also use.

Each library creates a so-called .pc file, for example, php.pc which is
installed to the pkgconfig subdirectory. For example,
/usr/lib/x86_64-linux-gnu/pkgconfig/php.pc

.pc file is created from a template .pc.in and gets some placeholders
replaced during the configuration phase of building to get the library
name, include flags etc.

PHP already extensively relies on pkg-config's interface for finding
certain dependencies during the build (libxml2, SQLite, OpenSSL, curl...)
but so far never implemented its own .pc file(s).

PHP could have two such .pc files. One for a global PHP installation as a
whole that PHP extensions can use (php.pc) and one for the embed SAPI to
embed PHP into an application (php-embed.pc)

Its usage is very similar to php-config script, i.e. getting build details.

See PR for details, I'll update it on the way what can be done.

Let me know if that's fine or is there some concern.

--000000000000522e49061c6e2c3f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<br><br>There is another pull request in preparation=
 that I&#39;d like to squeeze in the PHP-8.4 branch if it will possible to =
wrap it up until the feature freeze milestone:<br><a href=3D"https://github=
.com/php/php-src/pull/13755">https://github.com/php/php-src/pull/13755</a><=
br><br>In short, pkg-config is *nix command line utility to query installed=
 libraries on the system:<br><a href=3D"https://en.wikipedia.org/wiki/Pkg-c=
onfig">https://en.wikipedia.org/wiki/Pkg-config</a><br><a href=3D"https://p=
eople.freedesktop.org/~dbn/pkg-config-guide.html">https://people.freedeskto=
p.org/~dbn/pkg-config-guide.html</a><br><br>And pkgconf is a compatible mai=
ntained continuation/fork that many distributions might also use.<br><br>Ea=
ch library creates a so-called .pc file, for example, php.pc which is insta=
lled to the pkgconfig subdirectory. For example, /usr/lib/x86_64-linux-gnu/=
pkgconfig/php.pc<br><br>.pc file is created from a template .<a href=3D"htt=
p://pc.in">pc.in</a> and gets some placeholders replaced during the configu=
ration phase of building to get the library name, include flags etc.<br><br=
>PHP already extensively relies on pkg-config&#39;s interface for finding c=
ertain dependencies during the build (libxml2, SQLite, OpenSSL, curl...) bu=
t so far never implemented its own .pc file(s).<br><br>PHP could have two s=
uch .pc files. One for a global PHP installation as a whole that PHP extens=
ions can use (php.pc) and one for the embed SAPI to embed PHP into an appli=
cation (php-embed.pc)<br><br>Its usage is very similar to php-config script=
, i.e. getting build details.<br><br>See PR for details, I&#39;ll update it=
 on the way what can be done.<br><br>Let me know if that&#39;s fine or is t=
here some concern.</div>

--000000000000522e49061c6e2c3f--