My understanding is that the overall intent of all the LGPL/GPL licenses is to always give
the end user the ability to update or alter the open source modules.
When everything is open source as required by GPL, then everything is easy as the end user
has all the source and can modify things however he pleases.
With LGPL, it is possible that some of the code for a project/product is not open source.
In that case, the author must provide enough to allow the end user to be able to rebuild
the project/code/image if the end user should desire to modify any of the open source
components.
This is why LGPL requires that you provide objects of all the components, build scripts, etc...
(Or at least access to them, if not actually included in the product)
This allows an end user to modify or update an open source module and rebuild the code/project/product
even without having the source code to the closed source modules.
--- bill