|
|
|
|
|
|
by ikravets
3356 days ago
|
|
|
> It would be a great product if it un-bundled all the functions. Of course that would make it not-really-a-product, and they couldn't charge money for it as easily. But instead it's a monolith that offers you little wiggle-room. Could you explain in details? Do you know that you can create own development platform or add support for new embedded board wihout our support?
- http://docs.platformio.org/en/latest/platforms/custom_platfo... Yes, PIO Core 2.0 was monolitic. We rewrote it from scratch and announced decentrizlied PIO Core 3.0 in September, 2016:
- http://docs.platformio.org/en/latest/history.html#id7 > They've since added unit testing, but only using a framework of their choice. Which is nice, unless you already have a code base, or a preference for a framework. Which framework/workflow do you use for unit testing? |
|
|
Mayb ein a separate post. That's a lot details :-)
> Do you know that you can create own development platform or add support for new embedded board wihout our support?
But you would still force me to use PlatformIO as my build system, correct?
Now, assuming I accepted that:
How much effort is it for someone who doesn't know PlatformIO that well, doesn't know (or car about) SCons? Is it more or less effort than just using make/cmake/build system of my choice instead?
Can I be certain that I won't find out too late that I'm now locked in somehow? Are its processes truly flexible enough for what I need, and might need in the future?
Can I even (with reasonable effort) create new commands (e.g. platformio static_code_analysis) to shape PlatformIO to my needs?
> Yes, PIO Core 2.0 was monolitic. We rewrote it from scratch and announced decentrizlied PIO Core 3.0
Nice. Can you give me a quick pointer on how to just use the uploader portion of PlatformIO given I already have binaries at some location?
> Which framework/workflow do you use for unit testing?
The one that makes the most sense. If I get to pick, I like to use Catch. But since the decision tends to have already been made for me (through existing test suites, or coworker's preferences), I use whichever is most practical.
Or even several in parallel, as is the case on my current project.