From 32120ea2dc49900c7908b4da4e1bb4599f2ab224 Mon Sep 17 00:00:00 2001
From: whitequark <whitequark@whitequark.org>
Date: Fri, 21 Jul 2017 18:20:59 +0000
Subject: [PATCH] CONTRIBUTING, README: add XCode instructions.

---
 CONTRIBUTING.md | 11 +++++++++--
 README.md       |  6 ++++++
 2 files changed, 15 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a3581647..0163bd2e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -202,9 +202,16 @@ The Windows releases include the debug information on the GitHub
 
 ### Debugging a custom build
 
-If you are building SolveSpace yourself on a Unix-like platform,
+If you are building SolveSpace yourself on macOS, use the XCode
+CMake generator, then open the project in XCode as usual, select
+the Debug build scheme, and build the project:
+
+    cd build
+    cmake .. -G Xcode [other cmake args...]
+
+If you are building SolveSpace yourself on any Unix-like platform,
 configure or re-configure SolveSpace to produce a debug build, and
-then re-build it:
+then build it:
 
     cd build
     cmake .. -DCMAKE_BUILD_TYPE=Debug [other cmake args...]
diff --git a/README.md b/README.md
index ad3f8fd0..4433c84d 100644
--- a/README.md
+++ b/README.md
@@ -104,6 +104,12 @@ After that, build SolveSpace as following:
     cmake .. -DCMAKE_BUILD_TYPE=Release
     make
 
+Alternatively, generate an XCode project, open it, and build the "Release" scheme:
+
+    mkdir build
+    cd build
+    cmake .. -G Xcode
+
 The application is built in `build/bin/solvespace.app`, the graphical interface executable
 is `build/bin/solvespace.app/Contents/MacOS/solvespace`, and the command-line interface executable
 is `build/bin/solvespace.app/Contents/MacOS/solvespace-cli`.