On Tue, Nov 04, 2025 at 04:16:28AM +0800, Sune Brian wrote: > > On Tue, Nov 04, 2025 at 02:55:53AM +0800, Sune Brian wrote: > > > > OK. I was hoping that we could just automate as part of the regular > > > > build process seeing for example $(BOARD)/foo.xml and invoking the > > > > script to re-create foo.c and so forth, but that doesn't seem to be the > > > > case. So, no Makefile logic. We should then instead start on some > > My previous mail would like to know what need to be done for the > Makefile logic automation works as you expected. I can give it a try. > And what is the current difficult? > > Should the handoff compiled folder just place in the board/xxx/xxx > And let is auto build or not?
I think I'm not explaining things well enough because I don't quite understand the tooling well enough either. What I would like, but don't think is possible, is something like: $ make O=/tmp/myboard myboard_defconfig ... goes along and sees that boards/myvendor/myboard/myboard.xml exists. ... Runs the python script to re-create all of the C files, assuming xml ... is newer than the C files. ... Now compiles the new C files. But I also don't know how useful that work flow is. Which is why I'm going back to thinking that just having the tool, and documenting where it is / how to run it (under docs/boards/... so that it shows up in our generated docs) is likely good enough. -- Tom
signature.asc
Description: PGP signature
