Skip to content

Honor environmentSetupScript output when expanding non-VS kit environmentVariables (#4091)#4869

Merged
Omotola merged 4 commits intomainfrom
dev/oakeredolu/envpath
Apr 9, 2026
Merged

Honor environmentSetupScript output when expanding non-VS kit environmentVariables (#4091)#4869
Omotola merged 4 commits intomainfrom
dev/oakeredolu/envpath

Conversation

@Omotola
Copy link
Copy Markdown
Contributor

@Omotola Omotola commented Apr 7, 2026

Summary
Fix non-Visual Studio kit environment expansion so ${env:...} / ${env....} in environmentVariables uses the environment produced by environmentSetupScript (issue #4091).

Changes

  • Updated non-VS path in effectiveKitEnvironment() to expand with envOverride/penvOverride set to the post-script environment.

  • Preserved other caller-provided expansion options.

Added changelog entry under 1.23 Improvements with #4091.

Validation
Validated locally as seen in the screenshot, the Path variable prints both the extra paths added through the setup script and in the environmentVariables property.
image

@hanniavalera hanniavalera force-pushed the dev/oakeredolu/envpath branch from d125052 to 4280f26 Compare April 9, 2026 17:14
@Omotola Omotola enabled auto-merge (squash) April 9, 2026 17:15
@Omotola Omotola merged commit 24f6112 into main Apr 9, 2026
4 checks passed
@Omotola Omotola deleted the dev/oakeredolu/envpath branch April 9, 2026 17:37
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.

cmake-tools-kits environmentSetupScript having no effect on env.PATH variable

2 participants