Build folder per board and variant
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake, typescript, vscode
- Domain
- build-system, developer-experience
Research direction
Start with src/commands/getPaths.mts at the linked line and inspect how cmake.buildDirectory is handled. Then review tasks.json, where the Ninja build path is hardcoded, and determine how board and variant values should affect both paths. Done means separate build folders can be selected for each board and variant without manual settings or task edits.
Written by the indexing model from the issue text.
Description
Is it possible to set a build folder per board and per variant?
Like:
build/picow/rel
build/picow/deb
build/pico2w/rel
build/pico2w/deb
So looking into the source I came across this: https://github.com/raspberrypi/pico-vscode/blob/97c49e827e4da3bdee0b92aecce544d24033b73e/src/commands/getPaths.mts#L213
Sure enough you can already override the build directory from your settings.json by adding something like:
"cmake.buildDirectory": "${workspaceFolder}/build/pico2w/debug",
Now if only we could define this variable from the board and variant.
The build folder is also hardcode in the Ninja task in tasks.json so you will have to replace it with something like:
"args": ["-C", "${workspaceFolder}/build/pico2w/debug"],
- Dominant language
- TypeScript
- Stars
- 297
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/pico-vscode
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 78/100
raspberrypi/pico-vscode#282 ·
-
enhancement zephyr
Difficulty 1/5 Under an hour Newbie friendliness 72/100
raspberrypi/pico-vscode#268 · 1 comment ·
-
bug response awaited zephyr
Difficulty 4/5 3-5 days Newbie friendliness 25/100
raspberrypi/pico-vscode#281 · 2 comments ·
-
enhancement wontfix
Difficulty 5/5 Over a week Newbie friendliness 35/100
raspberrypi/pico-vscode#278 · 1 comment ·
-
enhancement zephyr
Difficulty 3/5 1-2 days Newbie friendliness 48/100
raspberrypi/pico-vscode#271 · 1 comment ·
All issues in raspberrypi/pico-vscode
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·