That's not entirely true. The LGPL requires that the end user be able to re-link the product with an API-compatible version of the LGPL-licensed library.
On platforms that support dynamic linking this is easy to allow - just package the LGPLed library as a dynamic library the user can easily replace. On platforms that don't (e.g. iOS) it's harder, and I believe it's still 'gray' what's required in practise - or even if the requirement is possible to satisfy. Some will say if you supply object files so that the end user can relink, that's fine.