Hi,
I'm adding custom (platform) targets via AddCustomTarget() and encountered inconsistent behavior.
Issue
- When running
pio remote run -t custom_target, they are locally filtered out because they don't belong to predefined categories such as clean or fs family.
- As a result, custom targets are silently ignored in the local execution (maybe they ran on remote).
Expected
Custom targets are
- executed locally, or
- on both machines.
Question
- Is there a way to mark a custom target as “allowed for local execution”?
- Can the filtering logic be bypassed or extended so that custom targets are passed through to local
cmd_run?
I think forcing remote option (-r) is not the solution I'm looking for.
Thank you.
Hi,
I'm adding custom (platform) targets via
AddCustomTarget()and encountered inconsistent behavior.Issue
pio remote run -t custom_target, they are locally filtered out because they don't belong to predefined categories such ascleanorfsfamily.Expected
Custom targets are
Question
cmd_run?I think forcing remote option (
-r) is not the solution I'm looking for.Thank you.