Espressif idf refuses to clean shared VisualGDB build directory

[gojimmypi]

This is the same as wolfSSL/wolfssl#6057 but as applied to this repo.

Version

current master branch

Description

Currently the project files for the VisualGDB Extension for Visual Studio are located in the same directory as the main wolfSSL project. For example: TLS13-ENC28J60-client. The problem with this is both the command-line idf.py build and VisualGDB both use the local ./build directory.

Although VisualGDB will gracefully clean the directory, the commandline idf.py fullclean is a bit more prudent, and will not clean the build the directory if (apparently extra) VisualGDB build files are found. The idf build instead gives an error such as this:

Executing action: fullclean
Directory '/mnt/c/workspace-PR/wolfssl/IDE/Espressif/ESP-IDF/examples/wolfssl_test/build' doesn't seem to be a CMake build directory. Refusing to automatically delete files in this directory. Delete the directory manually to 'clean' it.
/mnt/c/workspace-PR/wolfssl/IDE/Espressif/ESP-IDF
Failed in test

I plan to move the project files to a new VisualGDB subdirectory in the currently open "no setup" PR #6018 to better support my upcoming changes to the compileAllExamples.sh.

The VisualGDB build files will then be in sampleProject/VisualGDB/build and the regular idf.py build files will be in sampleProject/build.

This will also help declutter the project directory as more VisualGDB project files are added that target different chipsets and different versions of the ESP-IDF.

See wolfSSL/wolfssl#6234 for a roadmap of Espressif updates.