When building Drosera as a universal binary on a PowerPC machine, linking fails. The command I am using to build is: ./WebKitTools/BuildSlaveSupport/build-launcher-app ARCHS="ppc i386" SDKROOT_i386="/Developer/SDKs/MacOSX10.4u.sdk" I will attach the relevant portion of the build error shortly. The problem relates to the linker resolving paths in the WebKit.framework binary relative to the SDK root, not the file system root.
Created attachment 11101 [details] Build error
A workaround for the dev-tools lameness is to specify that WebCore and JavaScriptCore should be linked against in the Drosera project file. This clearly breaks in the case that WebKit is built as an umbrella framework, but it works well enough for the open source side of things.
Created attachment 11102 [details] Rough patch for consideration I'm not going to flag this patch for review just yet as it is very likely to break Drosera builds completely if WebKit is built as an umbrella framework. I'm not sure how big an issue this is, but I dare say that TimH will know.
I think using -weak_framework WebCore -weak_framework JavaScriptCore will do the trick. This will link with the built versions if they are found, and if not it should still build against the system umbrella framework on Leopard.
Created attachment 11137 [details] Use -weak_framework
Landed in r17119.