On Fri, Aug 25, 2023 at 9:38 AM Sebastien Lorquet wrote: > If you need to build twice, build twice, one project for h7, one project > for m4, then one python or other script to combine the images.
Some thoughts on this part :-) Yes, I agree here, and also proposed that with a several examples. New script would be a proof of concept if that kind of build is possible and how things work in reality. New script would be addition and non invasive functionality. New script would not flip all make build system upside down with a possibility of breaking backwards compatibility because build system remains untouched. New build script may create out-of-tree copy of the sources and configuration for a specific make build then link the results into a single firmware image. New script may leverage new cmake build with out-of-tree objects and binaries if make build is not good enough. New script, when verified and accepted, can be added to the upstream, providing additional optional functionality, just as most new things are added - use only when needed and stay in harmony with what is already here. I also use build scripts in my projects. New script is a good first step to prove if this kind of build is possible. If that works and author has time to update make build system with a new out-of-tree features _that_will_not_break_anything_ and _provide_full_backwards_compatibility_ (I gave FreeBSD build system as an example) that would seem to be time to discuss the _non_breaking_ change when we have something to discuss on. But this seems really lots of work that can be spared with a simple additional optional script. There are lots of ways to achieve the goal, in theory anything is possible, in reality it is always matter of work-time-cost. Not sure if that sounded clear enough in my previous reply, but this kind of build seems already possible, I work that way, with a different approach to build and project organization and zero upstream modifications. Why change the defaults for everyone because of a specific setup? Defaults should stay untouched :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
