129499 2014-02-28 11:26:52 -0800 In Xcode builds, WebKitLibraries aren't copied into BUILT_PRODUCTS_DIR 2015-09-10 15:22:55 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 132619 P2 Normal --- 1 bburg webkit-unassigned aestes fpizlo joepeck mitz oldest_to_newest 985654 0 bburg 2014-02-28 11:26:52 -0800 For open source builds, it seems you must first run build-webkit at the command line because copy-webkitlibraries-to-product-directory is never invoked by the Xcode projects. However, build-webkit doesn't expose any way to change the build root. This is a pain if you have a feature flag and want one svn checkout but two build directories to test the build with/without the flag enabled. So I have to manually execute the script: perl Tools/Scripts/copy-webkitlibraries-to-product-directory --wksi /Users/bburg/repos/webkit-patches/OpenSource/WebKitBuild/Vanilla/Debug Is there something I'm missing here? 1124255 1 bburg 2015-09-08 09:30:05 -0700 I can't directly verify this bug anymore, but it seems it should be fixed by the adjustments to product directory lookup made awhile ago. *** This bug has been marked as a duplicate of bug 132619 *** 1124292 2 aestes 2015-09-08 10:48:14 -0700 copy-webkitlibraries-to-product-directory is now executed as a build pre-action when you're using a workspace. I'm not sure when that was added. 1124293 3 aestes 2015-09-08 10:49:41 -0700 (In reply to comment #2) > copy-webkitlibraries-to-product-directory is now executed as a build > pre-action when you're using a workspace. The WebKit workspace, that is. 1125047 4 aestes 2015-09-10 15:22:55 -0700 One more thing to note: you actually can tell build-webkit to use a different build directory by setting $WEBKIT_OUTPUTDIR in the environment.