'idf.py -B MyBuildDir all' creates folder called 'mybuilddir' (all lower-case) (IDFGH-8858) #10282
Closed
3 tasks done
Labels
Resolution: Done
Issue is done internally
Status: Done
Issue is done internally
Type: Bug
bugs in IDF
Answers checklist.
IDF version.
ESP-IDF v5.0.0
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
> cd %userprofile%\esp
> xcopy /e /i %IDF_PATH%\examples\get-started\hello_world hello_world
> cd %userprofile%\esp\hello_world
> idf.py -B MyBuildDir set-target esp32c3 <-- specified build directory name contains upper- & lower-case letters
Adding "set-target"'s dependency "fullclean" to list of commands with default set of options.
Executing action: fullclean
Build directory '%userprofile%\esp\hello_world\mybuilddir' not found. Nothing to clean. <-- build directory name changed to all lower-case letters
Executing action: set-target
Set Target to: esp32c3, new sdkconfig created. Existing sdkconfig renamed to sdkconfig.old.
Running cmake in directory %userprofile%\esp\hello_world\mybuilddir <-- build directory name changed to all lower-case letters
...
What is the actual behavior?
> cd %userprofile%\esp
> xcopy /e /i %IDF_PATH%\examples\get-started\hello_world hello_world
> cd %userprofile%\esp\hello_world
> idf.py -B MyBuildDir set-target esp32c3 <-- specified build directory name contains upper- & lower-case letters
Adding "set-target"'s dependency "fullclean" to list of commands with default set of options.
Executing action: fullclean
Build directory '%userprofile%\esp\hello_world\MyBuildDir' not found. Nothing to clean. <-- build directory name as specified
Executing action: set-target
Set Target to: esp32c3, new sdkconfig created. Existing sdkconfig renamed to sdkconfig.old.
Running cmake in directory %userprofile%\esp\hello_world\MyBuildDir <-- build directory name as specified, i.e. unchanged
...
Steps to reproduce.
Build or installation Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: