Say I have a project which extendsmodm:disco-f469ni. Note that it hasa significant number of files, some of which aren't included by other targets. Now, I change my project to instead extendmodm:disco-f429zi. I runlbuild clean (optional) andlbuild build again. While the core board source files have been updated, theREADME.md and miscellaneous support files from the other board were left behind.

The output fromlbuild clean:

...Removing modm\src\modm\architecture\interface\spi_master.hppRemoving modm\src\modm\architecture\utils.hppRemoving modm\src\modm\board.hppRemoving modm\src\modm\board\board.cppRemoving modm\src\modm\board\board.hppRemoving modm\src\modm\driver\inertial\l3gd20.hppRemoving modm\src\modm\driver\inertial\l3gd20_impl.hpp...

It seems strange to me in general thatlbuild never seems to remove many of the files in the build tree. I have a diffhere which shows the changes made bylbuild clean. What am I missing? Doeslbuild only remove particular files, e.g. files that were generated via template?

While the left-over files might have technical ramifications if you are using a custom build configuration, for me this caused a bit of confusion when I was trying to make a custom board configuration. I had originally intended to copy the files from the GitHub repo, butthis document suggested copying them out of the build tree after running it throughlbuild. If I did so after changing my board configuration I'd be left with extra files that weren't needed and said they were for a different board.