2025-10-01 1:00 AM
I'm using CMake presets to setup a bunch of variables (ccache launcher, build type, toolchainfile, binaryDir).
My binaryDir is outside of source tree:
And vscode configure fails to find arm-none-eabi-gcc, it seems that the process seeks the .settings/bundles.store.json to find the correct gnu-tools-for-stm32 but it fails since it look up cmake binary dir instead of cmake source dir.
Copying my .settings directory does fix it, but I have multiple projects lying on the same place and I don't want to mix their settings.
Is this an intended behavior or should the .settings files be searched in source dir instead ?
Thanks
2025-10-01 1:35 AM
@stephane0 Thank for this valuable feedback.
Yes having the CMake binaryDir inside the project tree is a constraint we have.
Similarly you must open a folder which contains the top CMakeLists.txt file of your project as another hard constraint.
Such may evolve in the future however as per of today we don't have other option.
2025-10-01 1:49 AM
Ok @Julien D , thanks for the clarification.