Does using CLion solve these vscode issues?

PlatformIO IDE
,
1

PlatformIO is great! There are only a couple of things that have been bothering me lately, and both of them are related to vscode:

  • The MS c/c++ extension won’t work with vscodium or any non-MS build of vscode, but it’s required to run pio.
  • The c/c++ extension also doesn’t handle non-standard type qualifiers used by embedded compilers, such as SDCC’s __data, __xdata. etc. creating a mess of squiggles and making the actual mistakes harder to spot.

These problems have been around a while and so I was wondering if that’s what the support for CLion was intended to address, or if there’s some other eventual plan.

1 Like
2

As the platformio plugin for clion is written by jetbrains too, perhaps you should better post this in a jetbrains forum :wink:

3

Ok, sorry I hadn’t looked into it enough to even know jetbrains wrote it. I had assumed it was officially supported since it’s in the PlatformIO docs.

4

Hard to say exactly what the distribution of tasks between the two looks like as the plugin page links back to platformio. I think, posting in both areas would double the chances to get an answer.