Hello,

first of all, another great update of VisualGDB. Thank you very much.
I don’t visity your website frequently (maybe every 2-3 months) but each time, or almost each time, VisualGDB once again has improved.

Now with your extended support of Mbed OS, especialy since you utilize med-cli, I’d like to raise a question I already asked ~1 year or so ago, just in a newer fashion.

Imagine having several Mbed OS projects simultaniously. If each of these projects incorporate an individual copy of mbed-os (the Mbed OS directory), this takes up a lot of space. This only makes sence if your projects refer to different version of Mbed OS.

Please let me elaborate.
Currently we use KEIL µVision5 to develop Mbed OS projects. To save space and keep projects indepedant from the actual mbed-os diretory we use the following folder-structure.

root
|– mbed-os_v50904
|– mbed-os_v50907
|– mbed-os_v51001
|– Project01
|– source
|– include
|– main.cpp

We achieve this by using the mbed-cli python tools by exporting a Mbed OS project to a specific folder, refering to a location where the ‘mbed-os’ folder is located.

Example:
python.exe ..\mbed-os_v50907\tools\project.py -m NUCLEO_F767ZI -i uvision5 –source . –source ../mbed-os_v50907

This exports an Mbed OS project based on mbed-os-5.9.7 (the git-branch was previously cloned to ../mbed-os_v50907, relatie to the projet folder) for µVision5. The same would obviously be possible for projects based on a make-file utilizing the ARM-GNU compiler.

Example (makefile + vsCode):
python.exe ..\mbed-os_v50907\tools\project.py -m NULEO_F767ZI -i vscode_gcc_arm –source . –source ..\mbed-os_v50907 –profile ../mbed-os_v50907/tools/profiles/debug.json

Changes withing a project, made to the underlying mbed-os project a handled via utilizing ‘.mbedignore’ featues during project export. Individual files mentiong within ‘.mbedignore’ are ignored / not reference to the actual project and therefore can be ‘overwritten’ by the project, by replacing / offering an alternative file for the ignored one.

Soo…. I now told you a lot about his and that, but to the point (TL;DR)

TL;DR

• Would it be possible to implement a feature in the Mbed OS wizard to either refer to an already existing mbed-os projectfolder instead cloning an incorporating a ‘new’ one?
• Or, is it possible to automaticaly refer an already existing project to another ‘external’ mbed-os folder?
  E.g. ../mbed-os_v50907?

Greetings,
Christian