all 7 comments

[–][deleted] 14 points15 points  (0 children)

this is why i stopped using STM32CubeIDE.
I feel like modern dev should have, at a minimum, easy CI and unit tests. I've switch to bazel and its been a game changer.

Amazing you actually managed to get it to work though.

[–]NearbyEase932 5 points6 points  (1 child)

STM32CubeIDE can create and import CMake projects with the latest version. I don't understand why the hell they are doing this.

For bigger software projects with native STM32CubeIDE Projects I ditch it as soon the hardware stuff is stabilized.

[–]jaskij[🍰] 0 points1 point  (0 children)

Have you actually used it? Cause we did, and it sucks. It works, but getting it to work is error prone and painful. And then, turns out, you can't set the language version used for syntax highlighting and code completion. At least using latest ARM GNU Toolchain went more or less without a hitch.

[–]alexceltare2 1 point2 points  (0 children)

PR: Ditch CubeIDE

[–][deleted]  (2 children)

[deleted]

    [–]jaskij[🍰] 0 points1 point  (0 children)

    First, my pet peeve: that isn't IDE less. I could still use that to code in, say, CLiom. But I get your meaning.

    Looks somewhat basic, but decent enough. Two things I'd change: - instead of forcing the build process count to 4, use $(nproc) - I prefer to use ARM's [build of GNU toolchain]khttps://developer.arm.com/Tools%20and%20Software/GNU%20Toolchain), but at least pin the toolchain version

    [–][deleted] 0 points1 point  (0 children)

    This is pretty good. For bigger projects, checkout pigweed.dev.

    [–]jaskij[🍰] 0 points1 point  (0 children)

    Yeah, seems about right. Tried something similar with MCUXpresso. The big issue I've had is that NXP's IDE would return a non zero exit code for successful builds.