Changeset 174033 in webkit

Timestamp:

Sep 26, 2014, 10:18:55 PM (10 years ago)

Author:

ap@apple.com

Message:

WebKit top of tree sources won't build in 10.9 w/ Xcode 6.0.1
​https://bugs.webkit.org/show_bug.cgi?id=137053

Patch by David Gatwood. Reviewed, tweaked and landed by Alexey Proskuryakov.

Explain that to build from Xcode, one needs to build from command line once first.

Removed a Windows section that explained how to launch cygwin shell, which was
silly given that we then link to a long document explaining further steps.

• building/build.html:

Location:

trunk/Websites/webkit.org

Files:

• ChangeLog (modified) (1 diff)
• building/build.html (modified) (2 diffs)

trunk/Websites/webkit.org/ChangeLog

@@ +1 @@
+2014-09-26  Alexey Proskuryakov  <ap@apple.com>
+
+        WebKit top of tree sources won't build in 10.9 w/ Xcode 6.0.1
+        https://bugs.webkit.org/show_bug.cgi?id=137053
+
+        Patch by David Gatwood. Reviewed, tweaked and landed by Alexey Proskuryakov.
+
+        Explain that to build from Xcode, one needs to build from command line once first.
+
+        Removed a Windows section that explained how to launch cygwin shell, which was
+        silly given that we then link to a long document explaining further steps.
+
+        * building/build.html:
+
 2014-09-24  Langó László  <llango.u-szeged@partner.samsung.com>
 

trunk/Websites/webkit.org/building/build.html

@@ -6 +6 @@
 <h2>Building WebKit</h2>
 
-Building WebKit requires that you have the proper <a href="tools.html">developer tools
-installed</a> and that you have a copy of the <a href="checkout.html">WebKit source tree</a>.
+<p>Building WebKit requires that you have the proper <a href="tools.html">developer tools
+installed</a> and that you have a copy of the <a href="checkout.html">WebKit source tree</a>.</p>
 
 <div class="windows-instructions">
 <h4>Windows</h4>
-<ol>
-<li><p>Open a Cygwin Shell (if not already open from checking out sources)</p>
-<p>Double-click the Cygwin icon on your Desktop to launch a new shell.
-</ol>
+<p>Building on Windows requires a few more steps.  For details, see <a href="http://trac.webkit.org/wiki/BuildingOnWindows">http://trac.webkit.org/wiki/BuildingOnWindows</a>.</p>
 </div>
 
@@ -31 +28 @@
 place the build products there.</p>
 
-<div class="windows-instructions">
-<h4>Windows</h4>
-<p>Building on Windows requires a few more steps, you should look at: http://trac.webkit.org/wiki/BuildingOnWindows</p>
+<p>Once your build has finished, you can <a href="run.html">run Safari using
+your custom WebKit build.</a></p>
+
 <p>Don't forget that if you have any questions or problems building WebKit, feel free to <a href="/contact.html">get in touch!</a></p>
-</div>
-
-<p>Once your build has finished, you can <a href="run.html">run it inside
-Safari.</a></p>
-
-<h2>Building WebKit from Xcode</h2>
-<p>To build from within Xcode, you can use the WebKit workspace. Ensure that the Products and Intermediates locations for the workspace match those used by <code>build-webkit</code> by choosing File > Workspace Settings and clicking the Advanced button, selecting Custom, Relative to Workspace, and entering WebKitBuild both for Products and for Intermediates. Note that if you have specified a custom build location in Xcode preferences, then you don&rsquo;t need to do this.</p>
 
 <h2>Setting a Default Configuration</h2>
-<ol>
-<li><p>To set a default build configuration for <code>build-webkit</code> and
+<p>To set a default build configuration for <code>build-webkit</code> and
 other <a href="/coding/scripts.html">scripts</a>, use the
 <code>set-webkit-configuration</code> script:</p>
 <p class="code">set-webkit-configuration --debug</p>
 <p class="code">set-webkit-configuration --release</p>
-</li>
+</ol>
+
+<h2>Building WebKit from Xcode</h2>
+<p>To build from within Xcode, you can use the WebKit workspace.  Before you build in Xcode:</p>
+
+<ol>
+<li>Build WebKit at least once using the command-line instructions above.  Be sure to build using
+    the same configuration on the command line as you intend to use in Xcode (typically debug).</li>
+<li><p>Ensure that the Products and Intermediates locations for the workspace match those used by <code>build-webkit</code> by choosing File > Workspace Settings. Then click the Advanced button, select Custom, Relative to Workspace, and enter <code>WebKitBuild</code> for both Products and Intermediates.</p>
+    <p>Note that if you have specified a custom build location in Xcode preferences, then you don&rsquo;t need to do this.</p></li>
+<li>If you get unexpected include or linker errors, try deleting the entire WebKitBuild directory, then rebuilding
+    on the command line <b>before</b> you try to build in Xcode.</li>
 </ol>