Richard recently introduced a call to "bitbake build-sysroots" at the end of the eSDK installation (in ext-sdk-prepare.py), and as a result we now see a two full parses of all the recipes when installing the eSDK. The underlying cause for this is uninative which doesn't fully activate on the first execution of bitbake but does on the second, so this isn't especially new - it's just more apparent now vs earlier where the second parse was triggered the first time we run devtool within the installed SDK.

This is really poor experience - there must be a way to avoid this second parse which is doing nothing for us.