update README for Xcode project

Author: jack68k

xcode/Capstone.xcodeproj/project.pbxproj

@@ -224,6 +224,7 @@
 		21CBA9C52F6B8643009FC2DD /* tricore.h */ = {isa = PBXFileReference; lastKnownFileType = sourcecode.c.h; path = tricore.h; sourceTree = "<group>"; };
 		21CBA9C62F6B8643009FC2DD /* wasm.h */ = {isa = PBXFileReference; lastKnownFileType = sourcecode.c.h; path = wasm.h; sourceTree = "<group>"; };
 		21CBA9C72F6B8643009FC2DD /* xtensa.h */ = {isa = PBXFileReference; lastKnownFileType = sourcecode.c.h; path = xtensa.h; sourceTree = "<group>"; };
+		21CBA9D72F6B8EC8009FC2DD /* README.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = README.md; sourceTree = "<group>"; };
 		DC474F6819DE6F3B00BCA449 /* Capstone.framework */ = {isa = PBXFileReference; explicitFileType = wrapper.framework; includeInIndex = 0; path = Capstone.framework; sourceTree = BUILT_PRODUCTS_DIR; };
 		DC474F6B19DE6F3B00BCA449 /* Info.plist */ = {isa = PBXFileReference; lastKnownFileType = text.plist.xml; path = Info.plist; sourceTree = "<group>"; };
 		DCA3577B1BC2C0290094BB3F /* M68KDisassembler.c */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.c; path = M68KDisassembler.c; sourceTree = "<group>"; };
@@ -345,6 +346,7 @@
 		DCFE239919DDCB4900EF8EA9 = {
 			isa = PBXGroup;
 			children = (
+				21CBA9D72F6B8EC8009FC2DD /* README.md */,
 				DCFE249D19DDCDEE00EF8EA9 /* cs.c */,
 				21CBA9B12F6B7FF6009FC2DD /* Mapping.c */,
 				DCFE249E19DDCDEE00EF8EA9 /* MCInst.c */,

xcode/README.md

@@ -2,25 +2,35 @@ Xcode Project for Capstone
 ================================================================================
 
 The *Capstone.xcodeproj* project is an Xcode project that mimics the Visual
-Studio solution for Capstone. It embeds nicely into Xcode workspaces. It has 13
-targets, two of which are the most likely to be of interest:
+Studio solution for Capstone. It embeds nicely into Xcode workspaces. It has 3
+targets:
 
 * CapstoneStatic, producing `libcapstone.a`, Capstone as a static library;
 * CapstoneDynamic, producing `libcapstone.dylib`, Capstone as a shared library;
-* test, test_arm, test_aarch64, test_detail, test_mips, test_ppc, test_skipdata,
-	test_sparc, test_systemz, test_xcore, testing all the things.
+* CapstoneFramework, producing `Capstone.framework`, Capstone as a macOS
+  framework bundle containing the library and public headers.
 
 The project is configured to include all targets and use the system
 implementations of `malloc`, `calloc`, `realloc`, `free` and `vsnprintf`. This
-can be modified by editing the *Preprocessor Macros* build setting of either
-CapstoneStatic or CapstoneDynamic, whichever you plan to use. These settings are
-all at the target level: no specific overrides were used at the project level.
+can be modified by editing the *Preprocessor Macros* build setting of the
+target you plan to use. These settings are all at the target level: no specific
+overrides were used at the project level.
 
-### A Word of Warning: Static vs. Shared Library
+### Building
+
+The project can be built in Xcode or using `xcodebuild`:
+
+```sh
+xcodebuild -target CapstoneStatic -configuration Release
+xcodebuild -target CapstoneDynamic -configuration Release
+xcodebuild -target CapstoneFramework -configuration Release
+```
+
+### Including the Xcode project in a workspace
 
 There is a bug in how Xcode handles static libraries and dynamic libraries of
 the same name. Currently, if you integrate the Capstone project in a workspace
 and both the static *and* the dynamic libraries are built, if you try to link
 against either, you will *always* link against the dynamic one. To work around
 this issue, you can avoid building the dynamic library if you don't plan to use
-it, or you could change the *Product Name* build setting of either.
+it, or you could change the *Product Name* build setting of either.