Skip to content

Using vs17 for compilation going forward#1570

Merged
jahnvi480 merged 3 commits intodevfrom
jahnvi/windows2022
Feb 10, 2026
Merged

Using vs17 for compilation going forward#1570
jahnvi480 merged 3 commits intodevfrom
jahnvi/windows2022

Conversation

@jahnvi480
Copy link
Copy Markdown
Contributor

This pull request simplifies the logic for determining the compiler version in the buildscripts/buildtools.py script. The function now always sets the compiler to vs17 instead of selecting it based on the PHP version.

Build tools logic simplification:

  • The compiler_version method in buildscripts/buildtools.py was updated to always set self.vc to 'vs17', removing the previous conditional logic that selected the compiler based on the PHP version.

Copy link
Copy Markdown
Collaborator

@David-Engel David-Engel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm guessing the real purpose of this PR was to get the pipelines running a bit faster to address the macOS job 60 minute timeout failures. That was accomplished by the infinite job timeout of 0 (we should just bump that up incrementally, not to infinite). The brew and git changes might save a minute or two. The vs17-noly compilation won't save any time in the macOS job. I think that change is a bit premature unless PHP 8.3 can also be compiled by vs17.

Comment thread azure-pipelines.yml Outdated
Comment thread buildscripts/buildtools.py
@jahnvi480 jahnvi480 dismissed David-Engel’s stale review February 10, 2026 06:21

Have made the changes

@jahnvi480 jahnvi480 merged commit 56d8ea2 into dev Feb 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants