starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #2168] [MERGED] Create bx.cmd #24844

New Issue
Open
opened 2026-01-31 09:05:41 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:05:41 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/2168
Author: @zadjii-msft
Created: 7/31/2019
Status: ✅ Merged
Merged: 8/6/2019
Merged by: @zadjii-msft

Base: master ← Head: dev/migrie/f/bx.cmd

📝 Commits (5)

  • ae02a9c Try createing a script to only build the current working directory
  • 87571fb Merge remote-tracking branch 'origin/master' into dev/migrie/f/bx.cmd
  • 9d2c3ec Cleanup for PR
  • db0cd1f fix some bugs with building outside a project directory.
  • 44d23f4 PR nits

📊 Changes

5 files changed (+126 additions, -12 deletions)

View changed files

➕ tools/bcx.cmd (+7 -0)
📝 tools/bcz.cmd (+81 -10)
➕ tools/bx.cmd (+7 -0)
➕ tools/bx.ps1 (+28 -0)
📝 tools/bz.cmd (+3 -2)

📄 Description

Summary of the Pull Request

Adds a bx script that only builds the project in your current directory (and all the project's dependencies).

Detailed Description of the Pull Request / Additional comments

When we were in Windows, bz behaved a lot more like this, because obviously you don't want to build all of Windows when just working on the Console. However, when we moved the console to MsBuild, the solution only took like 4s to build, so we never bothered with creating a script to build a single project.

However, the Terminal projects take a very long time to build. So rebuilding the entire solution from the commandline became increasingly painful. This change should alleviate that pain. Hopefully quickly iterating on code in the Console codebase should be much more manageable with this change.

Building a single project in a solution is a little tricky however. You need to supply the target name to msbuild.exe, which is not as simple as just the Project's name or path. So we need to parse the sln's .metaproj file to correlate vcxproj file to target name. That's what bx.ps1 is for.

This change could use some extra love - generating the metaproj takes a little while, as does parsing it. There might be a way to only generate the metaproj if it's changed, I didn't really investigate this, but presumably it could be done with a powershell script. I'll leave that for another work item in the future. It's still much faster to build with bx than before, but it could be faster.

Validation Steps Performed

Built the thing using bx and bcx.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/2168 **Author:** [@zadjii-msft](https://github.com/zadjii-msft) **Created:** 7/31/2019 **Status:** ✅ Merged **Merged:** 8/6/2019 **Merged by:** [@zadjii-msft](https://github.com/zadjii-msft) **Base:** `master` ← **Head:** `dev/migrie/f/bx.cmd` --- ### 📝 Commits (5) - [`ae02a9c`](https://github.com/microsoft/terminal/commit/ae02a9c1040c12b3271756be8aeece470938c8ba) Try createing a script to only build the current working directory - [`87571fb`](https://github.com/microsoft/terminal/commit/87571fb5d89f0a14dcc5744b1cf3a5b0238a73a3) Merge remote-tracking branch 'origin/master' into dev/migrie/f/bx.cmd - [`9d2c3ec`](https://github.com/microsoft/terminal/commit/9d2c3ec2dd06f13b438bdf287e81695728b5b316) Cleanup for PR - [`db0cd1f`](https://github.com/microsoft/terminal/commit/db0cd1f587eadc74ff4364fdcdb4b1e523d849bc) fix some bugs with building outside a project directory. - [`44d23f4`](https://github.com/microsoft/terminal/commit/44d23f4fce61dfc949e1e842e5de53675e905d9e) PR nits ### 📊 Changes **5 files changed** (+126 additions, -12 deletions) <details> <summary>View changed files</summary> ➕ `tools/bcx.cmd` (+7 -0) 📝 `tools/bcz.cmd` (+81 -10) ➕ `tools/bx.cmd` (+7 -0) ➕ `tools/bx.ps1` (+28 -0) 📝 `tools/bz.cmd` (+3 -2) </details> ### 📄 Description <!-- Enter a brief description/summary of your PR here. What does it fix/what does it change/how was it tested (even manually, if necessary)? --> ## Summary of the Pull Request Adds a `bx` script that **only** builds the project in your current directory (and all the project's dependencies). <!-- Provide a more detailed description of the PR, other things fixed or any additional comments/features here --> ## Detailed Description of the Pull Request / Additional comments When we were in Windows, `bz` behaved a lot more like this, because obviously you don't want to build all of Windows when just working on the Console. However, when we moved the console to MsBuild, the solution only took like 4s to build, so we never bothered with creating a script to build a single project. However, the Terminal projects take a _very_ long time to build. So rebuilding the entire solution from the commandline became increasingly painful. This change should alleviate that pain. Hopefully quickly iterating on code in the Console codebase should be much more manageable with this change. Building a single project in a solution is a little tricky however. You need to supply the _target_ name to `msbuild.exe`, which is not as simple as just the Project's name or path. So we need to parse the sln's .metaproj file to correlate `vcxproj` file to target name. That's what `bx.ps1` is for. This change could use some extra love - generating the metaproj takes a little while, as does parsing it. There might be a way to only generate the metaproj _if it's changed_, I didn't really investigate this, but presumably it could be done with a powershell script. I'll leave that for another work item in the future. It's still much faster to build with `bx` than before, but _it could be faster_. <!-- Describe how you validated the behavior. Add automated tests wherever possible, but list manual validation steps taken as well --> ## Validation Steps Performed Built the thing using `bx` and `bcx`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:05:41 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#24844
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?