Skip to content

Adds VScode Task to improve internal workflows#3

Open
phevosccp wants to merge 2 commits into
mainfrom
workflow-improvements
Open

Adds VScode Task to improve internal workflows#3
phevosccp wants to merge 2 commits into
mainfrom
workflow-improvements

Conversation

@phevosccp

Copy link
Copy Markdown
Contributor

Description

After the VCPKG migration and open sourcing of the audio repository, previous internal workflows are now broken.
We still need a quick way to install the carbon-audio component into the monolith and this VScode task does exactly that.

How to use

  1. Hit CTRL+SHIFT+B the task will appear in a drop down menu
  2. Select the build preset e.g x64-Internal
  3. Next it will ask for a monolith root path e.g p4v/user/frontier_branch1

that's it, should build and install for you.

@phevosccp phevosccp requested a review from ccp-zoetrope June 30, 2026 13:16
ccp-zoetrope
ccp-zoetrope previously approved these changes Jun 30, 2026

@ccp-zoetrope ccp-zoetrope left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I was able to get this running locally and it works pretty well! You have to make sure to prefill the options for the monolith path in tasks.json before running it but that's just a minor qualm and not a major problem. I am not even sure it's possible in vscode to put a value like that in dynamically.

So this is good to go and a nice addition!

@ccp-zoetrope

Copy link
Copy Markdown
Member

Working with this more regularly, I am realizing that it is a problem that you have to pick the monolith path from a predefined set of options. Right now, your local path is actually set as the only option and every time I get this repo I will have to go into tasks.json and change it to my local path. If there is a way to do it through inputs that don't have to be submitted to github but only exist locally, that would be preferred.

@phevosccp

Copy link
Copy Markdown
Contributor Author

Working with this more regularly, I am realizing that it is a problem that you have to pick the monolith path from a predefined set of options. Right now, your local path is actually set as the only option and every time I get this repo I will have to go into tasks.json and change it to my local path. If there is a way to do it through inputs that don't have to be submitted to github but only exist locally, that would be preferred.

I tried to improve this by adding a new task for selectin the p4v branch, but feel free to commit to this branch too if you have other ideas regarding the workflow or improvements to suggest

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.

2 participants