M Starch

Makes sense to me. Currently we are avoiding updates to the Python Autocoder as FPP is now on the scene....but we should ensure this is included in the FPP autocoder.

Should have responded here: we do like the idea and our soliciting a set of names to add above the ones you have already added. Thanks for pointing this out!

F´ new is still something we support. It does need an update for FPP and the bug described here also needs to be fixed.

@pelmini take a look here. I think your "emptied out Ref" goal is a good starting place, and we can adjust from there. @ThibFrgsGmz we'll look into this!

That is the dream, but first we need solid toolchain implementations for these platforms...

#1443 has another CI improvement.

The constants are controlled by projects that adapt F´ and may be different per-deployment (at least some of them). Thus, although they change infrequently, a project may need to run...

@timcanham yaml was just a toy example to convey the use of a file that could be read in by many languages. I will take the action to talk to...

As of `v3.0.0` our constants are specified in FPP format. We could just use that as the format specification as it is already feeding constants in the C++ layer. All...

Does this problem persist when running: ``` fprime-util check native --all --jobs 1 ```