You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both terminal and debug console should build ServoCAN_debug env when debugging is run because ServoCAN_debug contains build_type = debug directive.
If problems with PlatformIO Build System:
Additional info
If I change the default env on the toolbar or modify "projectEnvName": to "ServoCAN_debug" manually then both terminal and debug_console build the same thing.
I used Python debugger to figure out what was going on.
So far I noticed that the terminal uses the following to determine the environment name,
Configuration
Operating system:
Windows 11
PlatformIO Version (
platformio --version
):6.1.6
Description of the problem
Debug console uses an environment from default_envs rather than one containing build_type = debug and the whole thing builds twice
Steps to Reproduce
platformio.ini
with the one provided here Debugger does not honor selected environment #4098 (comment)Actual Results
Terminal builds
ServoCAN_debug
env.Debug console clears build folder and build
ServoCAN
envExpected Results
Both terminal and debug console should build
ServoCAN_debug
env when debugging is run because ServoCAN_debug containsbuild_type = debug
directive.If problems with PlatformIO Build System:
Additional info
If I change the default env on the toolbar or modify "projectEnvName": to "ServoCAN_debug" manually then both terminal and debug_console build the same thing.
I used Python debugger to figure out what was going on.
So far I noticed that the terminal uses the following to determine the environment name,
platformio-core/platformio/debug/helpers.py
Lines 68 to 74 in 58a1d5d
while Debug console uses
platformio-core/platformio/run/cli.py
Lines 137 to 138 in 58a1d5d
I think both should use the same determination logic.
The text was updated successfully, but these errors were encountered: