What I means the full is that all config must pass the automation build and run the build system regularly like other host.
Yes, the problem is a circular one. Why is the native build always out of date? Because it is not tested. Why don't we test it? Because it is out of date.
There are only two ways to break that circular dependency: Remove it or make it work. There is less inertia to removing it but I don't think that is a good decision. Is it not motivated only by making the job easier?
I have not tried a native build in some time. I will try that later today. There is only one native build configuration in the repository: stm32f4discovery:winbuild. Let me experiment a little to see where things are.
