From this question on SO, I read that:
Proprietary Source code + LGPL Source code
- statically linked:
- Either you must release both parts as LGPL.
- Or provide everything that allow the user to relink the application with a different version of the LGPL source code. In this case the other requirements are the same as if it was dynamically linked.
So it does sound like providing object files is enough to satisfy LGPL in terms of statically linking a LGPL library to a proprietary code application. While the executable is statically linked, providing the object files allows the end user to recompile the application, linking to different version of the library.
Is this correct, and if not, then why?