'VS Code: What's the best practice to manage multiple apps built from the same codebase? Code has no projects
There is a common codebase with several applications (running on different MCUs) and a lot of shared code. As of now, all code is in one directory structure under a Code workspace. Different apps can be built by entering their folder and starting GNU make.
- In tasks.json there is one build task (with properly configured problem matcher) for each compiler. The build folder (options/cwd, and fileLocation for several problem matchers, and also cwd for the clean/clobber/deploy tasks) have to be updated all the time when building another app, and different build tasks have to be started for each compiler. Is there a better way to manage this? It would be great to share tasks.json, or the problem matchers in it between the apps.
- It would be nice to hide the folders of the other apps when
working on one app, but not hide the common files. As of now, I
listed all app folders under files.exclude in the workspace, and
comment out the apps that I actually want to see (and search in
them, resolve references etc...) It works, painfully, is there a
better way?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|