Adds VScode Task to improve internal workflows#3
Conversation
ccp-zoetrope
left a comment
There was a problem hiding this comment.
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!
|
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 |
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
that's it, should build and install for you.