CI: Build each project independently on Linux and Windows

[carlosperate]

As some projects are failing to build, I thought it might be good addition to the CI to build all projects in a workflow matrix to be able to see the build state of each of one them independently.
One disadvantage of this approach is that if a new algo is added it needs to be added to the list in the CI yaml file as well, but I also added a job to build all, in case the list is not updated.

Also added Windows runs, as sometimes something might work in one OS and fail in the other (fs case sensivitity, or path separators, usually being the most common causes). I didn't add macOS because that added another 48 jobs, and that might be too much.

[carlosperate]

Full disclosure, this step uses an Action I maintain, which facilitates Arm GCC installation (with caching, etc), but happy to change it to OS-specific steps if needed.

[flit]

Nice! Glad to hear know about this action!

[flit]

I have to admit I have mixed feeling about this. It's nice seeing the results per project directly on the main PR page. But, the number of jobs won't scale well, as you said, adding macOS would be probably too many jobs, and the actions yaml has to be updated manually as projects are added.

On first thought, what I think I'd prefer for the ideal situation is one job per OS, but with some scripting that adds an expected-failures list and reports the individual project failures so they show up in GH's checks page. However, given that this project isn't used much (compared to before we could extract algos from CMSIS-Packs), it's way too much to ask.

So, I think I'd actually prefer to just remove the broken projects from projects.yaml until they are fixed. And frankly, there's not much of a reason to fix them. Thanks to your recent fixes, only cc322sf and lpc54018 are still broken.

Could I ask you:

• Comment out broken projects from projects.yaml.
• Revert to one job per OS.
• Add macOS if it's not troublesome.

Thanks!

[carlosperate]

Sounds good!
One thing before making the changes:

So, I think I'd actually prefer to just remove the broken projects from projects.yaml until they are fixed. And frankly, there's not much of a reason to fix them. Thanks to your recent fixes, only cc322sf and lpc54018 are still broken.

These are broken with GCC, but they build successfully with uVision (haven't tried IAR). With that in mind do you still want to comment them out?

Is there a way for project generator to not build with with GCC but still build them with the other tools?