When selecting a prj.conf or a prj_${board}.conf as the configuration file, the extension would attempt to determine whether this would be the default configuration file chosen by the build system, and leave it out of the build command if it would be redundant.
Unfortunately, this mechanism did not cover all corner cases in the build system, and in some scenarios, the build would be misconfigured in ways that could be very hard to detect.
To fix this, we have made three changes to the configuration file setting:
- By default, the extension will now omit the configuration file argument from the build string, and use whatever the build system default is.
- If you explicitly pick a configuration file from the drop-down list, the extension will now pass this file to the build command, regardless of whether it will be redundant or not.
- When changing to a different board, the configuration file selection will always be reset to use the build system default, to prevent accidental selection of board-specific configuration files for the wrong board.