Repository navigation
Replies: 1 comment
|
I have seen this, just haven't had a time to look into it properly yet, last couple days have been very hectic, but I will try look into this next week 👍 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Would maintainers welcome a PR to enable the bundled
php/gdpackage, with configurable JPEG and FreeType support? I am opening this discussion before making PIE code changes, as requested by the contribution guide.Context
We use official PHP Docker images and currently build GD using
docker-php-ext-configure gd --with-freetype --with-jpegfollowed bydocker-php-ext-install gd. We would like to evaluate using PIE for this too, while preserving those capabilities.php/gd.ft2build.h: No such file or directoryrecorded as the reason.Current reproduction
PIE 1.5.2, PHP 8.5.12 NTS, Debian 12 (bookworm), Linux arm64. Using the official release PHAR in
php:8.5.12-fpm-bookworm, withlibtool,unzip,libpng-dev,libjpeg-dev, andlibfreetype-devinstalled:The installation fails during package resolution, before compilation. Using
--forcedoes not make the package available.Complete PIE output from the reproduction
pie show -v:pie install php/gd --force --no-interaction -vv:Preliminary build checks
Separately, I built
ext/gdfrom the PHPphp-8.5.12GitHub source archive in a Debian bookworm/arm64 container with the development libraries installed, usingphpize,./configure --with-php-config=/usr/local/bin/php-config, andmake:--with-jpeg --with-freetypesucceeded, reported both capabilities enabled, and passed PNG and JPEG encode/decode round trips. Font rendering has not been tested.These were standalone GD build checks, not successful PIE installations. I have not reproduced or established the cause of the original CI header failure, and have made no PIE implementation changes.
Proposed scope, subject to maintainer feedback
php/gdwhile preserving PIE's existing--forcerequirement for bundled extensions.Is this direction welcome, and is there existing work or another issue to coordinate with? I will wait for feedback before starting implementation or opening a PR. If accepted, please advise whether this should target
1.6.xas new support or1.5.xas a fix.All reactions