If it's dynamically linked, all they need to do is release the source.
EDIT: There are also makefiles provided in the release.
Are you sure there's a working build system included? There's a file named "Makefile", but it just includes "../Makefile.shared", which--as far as I can tell-isn't included. There's no XCode project file to be seen, so the build directions on webkit.org don't seem operative. Are you actually able to build this?
Unfortunately, I don't have access to my mac at the moment to actually tell you if this works.
Also, you can run 'make-generated-sources.sh' on pretty much any Linux or UNIX (probably including Cygwin).
Or maybe there is some common code within WebCore that is shared between Mac and iOS, and one of the files needs to import the WAK headers to compile correctly?
While it is fun to get worked up into a frenzy, I doubt this is an LGPL violation.
As static linking is covered by the LGPL, the source code for that (and other) classes must be made available, yet they are not. How is that not a LGPL violation?
(You can also see via the "class-dump" utility that there are many more WAK classes inside the WebCore binary. No source code has ever been released for those classes.)
For some reason, Apple does not include them in the iOS releases, in a violation of the LGPL.
http://opensource.apple.com/source/WebCore/WebCore-955.66.1/...
The source is here: http://opensource.apple.com/source/WebCore/WebCore-955.66.1/...
EDIT: I'm probably missing something, but it appears that the wak code was present since 1.0.
And, as saurik mentions here (http://news.ycombinator.com/item?id=2523786), they do not even release the full source code! Even if you ignore the point about building your own copy, they are still violating the LGPL: releasing the code to those "WAK" classes is not optional.