Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"pio test -c someconfig.ini" ignores "-c"

See original GitHub issue

PlatformIO Core. If you’ve found a bug, please provide an information below.

Configuration

Operating system: macOS

PlatformIO Version: 4.3.4

Description of problem

pio test -c configs/native.ini gives an error msg.
With pio run -c configs/native.ini, it works as expected.

Actual Results

The platformio.ini file is used, which does not contain a “native” env:

Error: Unknown environment names 'native'. Valid names are 'bluepill_f103c8'

The content of platformio.ini:

[platformio]
extra_configs = configs/bluepill_f103c8.ini

Issue Analytics

State:
Created 3 years ago
Comments:17 (8 by maintainers)

Top GitHub Comments

1reaction

jcwcommented, Aug 25, 2020

Great, thx. Yes, [env] is a very useful addition. And the above would scale nicely to [env:dev1], [env:dev2], etc to let me pick exactly the small subset of boards I am currently focusing on - even if configs/ ends up being huge.

Thanks Ivan. Fantastic job by you and your team.

1reaction

jcwcommented, Aug 25, 2020

The main platformio.ini can be something like:

[platformio]
extra_configs = configs/[a-z]*.ini
default_envs = disco_f407vg

[env]
test_filter = type

[env:disco_f407vg]
build_flags = -Wno-return-type -DNDEBUG
monitor_port = /dev/cu.usbmodem1462203
test_port = /dev/cu.usbmodem1462203

One minor issue remains: AFAIK, I can’t add to the build_flags setting in this setup. It would be nice to have the ini files have all the stuff essential for building as is, and then allow adding more flags in the above (or vice versa: have the ini files add to what is present in the platformio.ini file. But now we’re straying into wish-list territory 😃