-
-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared extension vs Windows #887
Comments
On Ubuntu xmlwriter, simplexml and tokenizer are all shared extensions. On Windows these are all compiled statically into the php binary so cannot be disabled. |
@shivammathur Thanks for the fast reply! Is there a list somewhere of which extensions are shared / can be disabled vs those that are compiled into the php binary ? |
I will try to add that to the wiki |
That was the first place I looked, so that would be awesome! ⭐ ⭐ ⭐ ⭐ ⭐ |
Added in the lists in wiki |
:hero: |
Hi @shivammathur, I'm currently working on some tests related to a CLI tool requirements check.
While doing so, I'm running into some issues related to "shared" vs non-shared extensions, in particular on Windows, and I'm struggling to find documentation on this. Maybe you could point me in the right direction ?
Here are some examples of things I'm running into:
Example 1
For this case, the intend of the test is to verify that the requirements check detects that the Tokenizer extension is missing.
On Ubuntu this works fine and the test correctly fails.
On Windows, the test passes, which leads me to believe that the Tokenizer extension was not disabled, so I presume this must be a "shared" extension which cannot be disabled ?
Example 2
For this case, the intend of the test is to verify that the requirements check detects that the XMLWriter extension is missing.
On Ubuntu this works fine and the test correctly fails.
On Windows, the test fails too, but on the
setup-php
set with the following error:The text was updated successfully, but these errors were encountered: