RE: VS Code keeps selecting wrong build configuration

Amanda Hsieh — Tue, 30 Jun 2026 19:08:51 GMT

If your project can run as expected, only the editor loaded the wrong file. Then, please ensure you select the correct app build folder to load the correct files every time, and open the files from the Details View. You can also open .config from the Output files to verify the config values.

RE: VS Code keeps selecting wrong build configuration

Will_20241202 — Tue, 30 Jun 2026 14:50:06 GMT

Hi Amanda,

I have the correct build targets showing up in the locations highlighted in your screen shot, but the editors still show the incorrect code paths as active. To be clear, the code builds and runs correctly, with the execution following the desired path, it's just really hard to trace through the code in the editors because the compile guards are drawing the values from a different build target. A toy example is shown below:

#if defined( CONFIG_BOARD_FOO_A )
	#define MY_CONSTANT (123)
#elif defined( CONFIG_BOARD_FOO_B )
	#define MY_CONSTANT (456)
#elif defined( CONFIG_BOARD_FOO_C )
	#define MY_CONSTANT (789)
#else
	#error "No recognized board defined!"
#endif

If I build against the target that uses BOARD_FOO_C I would expect the MY_CONSTANT to be shown as (789) and the line defining it as not dimmed out, but instead I see the line where it is defined as (123) as normal and the others are dimmed. As the defines propagate through the editors this results in the "Go To Definition" and "Go To Declaration" features picking the wrong code and hovering over expressions to see how they evaluate showing the wrong values.

RE: VS Code keeps selecting wrong build configuration

Amanda Hsieh — Mon, 29 Jun 2026 19:25:36 GMT

Hi Will,

Try selecting the app entry under the build configuration entry as the following figure:

Regards,
Amanda H.