I realize this is not the ideal place to post this, but I’ve
already posted my question to the webkit-dev list and it was suggested this may
be a general build question that would be more appropriate for an xcode
list. If there is a more appropriate list, please let me know.
I’m trying to recompile the webkit framework to be
usable as a private/embedded framework deployed with our application and
referenced by a relative path. Our application is a Java bundle, that
calls the webkit through a wrapper jnilib. I’ve seen many general
examples of using the @executable_path and @loader_path values to get compiled
framework that can be referenced in this way, and I’ve also run across
explanations for the install_name_tool and otool utilities to change references
in compiled libraries. All of these seem relatively simple and I’ve
tried various combinations of them, but with limited success.
At this point, I am not sure if there is a limitation to
referencing embedded frameworks from a java bundle, or some combination of the
jnilib we are using on top of the frameworks, or if there is there is a reason
that the webkit frameworks are not able to be compiled in this manner.
As for exactly what I’m doing, I’ve simply
downloaded the webkit frameworks, and followed instructions to compile via the
shell scripts (build-webkit). If I change all 4 projects INSTALL_PATH to
@loader_path/Frameworks, I can compile them successfully. I then copy
them to my jnilib project and I can compile that, but executing it from Java
does not work. My library fails to load, presumably because it’s
calling into the frameworks, which don’t load properly because of
pathing. To not draw this out too much, I’m getting the impression
that the WebKit.framework is being found, but the dependent frameworks (WebCore
and _javascript_Core) cannot be loaded for some reason.
If anyone has any experience on how to compile complex
frameworks for private distribution, or has links to any documentation related
to this, please let me know. Thank you.
-Adam.