Generate SwiftGRPC.xcodeproj in the top-level Makefile.

Generated projects were found to contain absolute paths,
which caused builds to fail when they were checked out in
other locations.

Author: timburks

Makefile

@@ -3,10 +3,16 @@ CFLAGS = -Xcc -ISources/BoringSSL/include
 
 LDFLAGS = -Xlinker -lz 
 
+all:
+	swift package generate-xcodeproj
+	swift build -v $(CFLAGS) $(LDFLAGS)
+	
+
 test:
 	swift build -v $(CFLAGS) $(LDFLAGS)
 	swift test -v $(CFLAGS) $(LDFLAGS) 
 
-clean :
+clean:
 	rm -rf Packages
 	rm -rf .build
+	rm -rf SwiftGRPC.xcodeproj

README.md

@@ -30,11 +30,19 @@ systems. Please see [DOCKER.md](DOCKER.md) and
 ## gRPC dependencies are vendored  
 
 Swift gRPC now includes vendored copies of the gRPC core 
-library and "BoringSSL", an OpenSSL fork that is used by
+library and **BoringSSL**, an OpenSSL fork that is used by
 the gRPC Core. These are built automatically in Swift Package
-Manager builds. The repository also includes SwiftGRPC.xcodeproj,
-an Xcode project which is automatically-generated by the Swift
-Package Manager.
+Manager builds.
+
+## Building with Xcode
+
+The top-level Makefile uses the Swift Package Manager to generate
+an Xcode project for the SwiftGRPC package. Due to present limitations
+in Package Manager configuration, the libz dependency is not included 
+in the generated Xcode project. If you get build errors about missing
+symbols such as `_deflate`, `_deflateEnd`, etc., you can fix them by
+adding `libz.tbd` to the **Link Binary With Libraries** build step of 
+the **CgRPC** target.
 
 ## Having build problems?