aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.md
diff options
context:
space:
mode:
authorGravatar Hoa V. DINH <dinh.viet.hoa@gmail.com>2015-01-19 14:11:57 -0800
committerGravatar Hoa V. DINH <dinh.viet.hoa@gmail.com>2015-01-19 14:11:57 -0800
commite386f023d84b74eaeb3b8f2fa1c92bfe27df4f7e (patch)
tree9421998e821989baaa93e90f8fca9adae649d3c0 /README.md
parent9358b2fda79ff8ef9ae712e76a05181536a2febd (diff)
Added Android to main README
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/README.md b/README.md
index 4e6539b5..b56858b4 100644
--- a/README.md
+++ b/README.md
@@ -17,6 +17,10 @@ MailCore 2 provides a simple and asynchronous Objective-C API to work with the e
Read [instructions for iOS/OSX](https://github.com/MailCore/mailcore2/blob/master/build-mac/README.md).
+### Build for Android ###
+
+Read [instructions for Android](https://github.com/MailCore/mailcore2/blob/master/build-android/README.md).
+
### Build for Windows ###
Read [instructions for Windows](https://github.com/MailCore/mailcore2/blob/master/build-windows/README.md).
@@ -27,7 +31,7 @@ Read [instructions for Linux](https://github.com/MailCore/mailcore2/blob/master/
## Basic IMAP Usage ##
-Using MailCore 2 is just a little more complex conceptually than the original MailCore. All fetch requests in MailCore 2 are made asynchronously through a queue. What does this mean? Well, let's take a look at a simple example:
+Using MailCore 2 is just a little more complex conceptually than the original MailCore. All fetch requests in MailCore 2 are made asynchronously through a queue. What does this mean? Well, let's take a look at a simple example:
```objc
MCOIMAPSession *session = [[MCOIMAPSession alloc] init];