-
-
Notifications
You must be signed in to change notification settings - Fork 326
Description
Hi!
I noticed that static-php-cli uses lib_libiconv_0 only in some extensions during the build process.
Since lib_libiconv_0 is licensed under GPLv3, I have a few questions regarding possible licensing implications:
When lib_libiconv_0 is used only by certain extensions, does the final static binary still become a GPL-derived work, effectively making the whole build subject to GPL terms?
Would this prevent distributing the static PHP binary under another license (such as the BSD) or bundling it with proprietary software?
Considering that the PHP License is incompatible with the GPL, could this create a legal or licensing conflict when building with extensions that depend on lib_libiconv_0?
Is there any alternative way to build these extensions without relying on the GPL version of lib_libiconv_0 — for example, using a BSD, MIT, or LGPL compatible implementation?
Thanks in advance for any clarification or suggestions on how to avoid license compatibility issues during compilation.