Good to know. Thanks for that update.

Since the user experience of mbed-src and mbed-dev is slow and clunky to move around, import and export how would you feel about having a repo for each target that only gets the updates that are relevant to the target. This breaks things a bit but the mbed.bld will obviously still exist. It would mean you still need to set the proper target and also have the *right* library imported. I have mixed feelings about this and wondering how power users would feel. IMO mbed-src (now mbed-dev) is only useful when debugging or bringing up new platforms. Feedback??

Maybe a separate topic would be good for this :).

In addition to the reasons you use, there is another one: Customizing. For example if you want a different clock setup for your board.

For starters: I definately see the problems you mention. The compiler gets close to crashing when you try to update the mbed-dev lib. Having it smaller/less clunky would definately be useful. I think going target specific would really be handy, not always perfect, but generally a better solution. Maybe manufacturer specific would be an inbetween option, although maybe for large ones, such as an STM, you still got a huge lib.

OK - Will start a separate thread about this. Good mention on the customization of clocks and hardware. Would be an interesting to see if getting a decent workflow is possible while tracking upstream changes :)