Updated EarlGrey Code to allow modules in the xcodeproj. Also changed…

… the ref-links in the docs

CHANGELOG.md

@@ -3,8 +3,8 @@
 First cup of EarlGrey.
 
 ```
-Baseline: [71b8374]
-   + [71b8374]: First version of EarlGrey.
+Baseline: [ac60060]
+   + [ac60060]: First version of EarlGrey.
 ```
 
 Initial release.

EarlGrey.xcodeproj/project.pbxproj

@@ -1097,6 +1097,7 @@
 				"CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "";
 				COPY_PHASE_STRIP = NO;
 				DEBUG_INFORMATION_FORMAT = dwarf;
+				DEFINES_MODULE = YES;
 				ENABLE_STRICT_OBJC_MSGSEND = YES;
 				ENABLE_TESTABILITY = YES;
 				GCC_C_LANGUAGE_STANDARD = gnu99;
@@ -1144,6 +1145,7 @@
 				"CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "";
 				COPY_PHASE_STRIP = NO;
 				DEBUG_INFORMATION_FORMAT = "dwarf-with-dsym";
+				DEFINES_MODULE = YES;
 				ENABLE_NS_ASSERTIONS = NO;
 				ENABLE_STRICT_OBJC_MSGSEND = YES;
 				GCC_C_LANGUAGE_STANDARD = gnu99;

README.md

@@ -18,24 +18,25 @@ line (using xcodebuild).
 
 ## Getting Started
 
-The EarlGrey documentation for users is located in the `EarlGrey/docs` folder.
+The EarlGrey documentation for users is located in the
+[EarlGrey/docs](https://github.com/google/EarlGrey/tree/master/docs) folder.
 To get started, review the EarlGrey features, check for backward compatibility,
 and then install/run EarlGrey with your test target. Once everything is
 configured, take a look at the EarlGrey API and start writing your own tests.
 
-  * [Features](./docs/features.md)
-  * [Backward Compatibility](./docs/backward-compatibility.md)
-  * [Install and Run](./docs/install-and-run.md)
-  * [API](./docs/api.md)
+  * [Features](https://github.com/google/EarlGrey/tree/master/docs/features.md)
+  * [Backward Compatibility](https://github.com/google/EarlGrey/tree/master/docs/backward-compatibility.md)
+  * [Install and Run](https://github.com/google/EarlGrey/tree/master/docs/install-and-run.md)
+  * [API](https://github.com/google/EarlGrey/tree/master/docs/api.md)
 
 ## Getting Help
 
 If you need help, several resources are available. First check the FAQ. If the
 answers you need are not there, read through the Known Issues. If you still have
 questions, contact us using our [Google group](https://groups.google.com/forum/#!forum/earlgrey-discuss).
 
-  * [FAQ](./docs/faq.md)
-  * [Known Issues](./docs/known-issues.md)
+  * [FAQ](https://github.com/google/EarlGrey/tree/master/docs/faq.md)
+  * [Known Issues](https://github.com/google/EarlGrey/tree/master/docs/known-issues.md)
 
 ## Analytics
 
@@ -53,7 +54,7 @@ setUp method:
 
 ## For Contributors
 
-Please make sure you’ve followed the guidelines in 
+Please make sure you’ve followed the guidelines in
 [CONTRIBUTING.md](./CONTRIBUTING.md) before making any contributions.
 
 ### Setup EarlGrey Project

docs/features.md

@@ -11,7 +11,7 @@ To support cases where you want to wait for some event to occur before the next
 EarlGrey provides Synchronization APIs that allow you to control EarlGrey's synchronization behavior. You can
 use these APIs to increase the stability of your tests.
 
-## Visibility Checks<a name="Visibility-Checks"></a>
+## Visibility Checks<a name="visibility-checks"></a>
 
 EarlGrey uses screenshot differential comparison (also known as 'screenshot diffs') to determine the
 visibility of UI elements before interacting with them. As a result, you can be certain that a user can see
@@ -24,7 +24,7 @@ interfere with this process.
 
 Taps and swipes are performed using app-level touch events, instead of using element-level event handlers.
 Before every UI interaction, EarlGrey asserts that the elements being interacted with are actually visible
-(see [Visibility Checks](#Visibility-Checks)) and not just present in the view hierarchy. EarlGrey's UI
+(see [Visibility Checks](#visibility-checks)) and not just present in the view hierarchy. EarlGrey's UI
 interactions simulate how a real user would interact with your app's UI, and help you to find and fix the
 same bugs that users would encounter in your app.