M Starch

Rename StandardTypes.hpp -> PlatformTypes.hpp

This is true. Installing the `gcc-arm-linux-gnueabihf` toolchain, and setting the RPI_TOOLCHAIN_DIR environment variable to the install directory should allow using the newer toolchain. i.e. ${RPI_TOOLCHAIN_DIR}/bin/ should contain the binary tools

Should update the CI build too.

I have yet to find a good way of dealing with Github Actions locally. I just push to github and see how it works out. Then adjust if it fails.

You can find the full logs by: 1. Clicking on "Summary" in the Actions' Left Pane 2. Scroll to the bottom to find the artifacts section 3. Downloading the rpi-logs...

If you are changing the compiler, you'll likely need to update the top of this file where it infers the toolchain path when not set as an environment variable: https://github.com/nasa/fprime/blob/devel/cmake/toolchain/raspberrypi.cmake

One other note: once the first stage (build and compile) passes, submit a PR to the fprime repo. The second stage action cannot run outside of `nasa/fprime`.

Also assigned you since you are working on this. If it becomes too much, we can reassign it.

This toolchain requires that the RPI tools be on the path and uses whatever it finds. If we go with this route, we'll need to update the the RPI README...

This would bring us full circle back to tHe original PI tool chain....Which doesn't support the on path programs