Skip to content

Commit 21bb6c2

Browse files
authored
Update README.md
1 parent bb7054f commit 21bb6c2

File tree

1 file changed

+47
-44
lines changed

1 file changed

+47
-44
lines changed

README.md

Lines changed: 47 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -28,71 +28,74 @@ Notice the API docs aren't totally up to date when it comes to latest Swift sign
2828

2929
#### [CocoaPods](https://cocoapods.org)
3030

31-
Add the following line to your Podfile:
32-
```ruby
33-
pod 'Parse'
34-
```
35-
Run `pod install`, and you should now have the latest parse release.
31+
Add the following line to your Podfile:
32+
```ruby
33+
pod 'Parse'
34+
```
3635

37-
If you wish to use the Facebook or Twitter utils or ParseUI,
38-
you can now leverage Cocoapods 'subspecs'
36+
Run `pod install`, and you should now have the latest parse release.
3937

40-
```ruby
41-
pod 'Parse/FacebookUtils'
42-
pod 'Parse/TwitterUtils'
43-
pod 'Parse/UI'
44-
```
38+
If you wish to use the Facebook or Twitter utils or ParseUI,
39+
you can now leverage Cocoapods 'subspecs'
4540

46-
Note that in this case, the Parse framework will contain all headers and classes, so you just have to use:
41+
```ruby
42+
pod 'Parse/FacebookUtils'
43+
pod 'Parse/TwitterUtils'
44+
pod 'Parse/UI'
45+
```
4746

48-
```swift
49-
import Parse
50-
```
47+
Note that in this case, the Parse framework will contain all headers and classes, so you just have to use:
5148

52-
```objc
53-
@import Parse;
54-
```
49+
```swift
50+
import Parse
51+
```
52+
53+
```objc
54+
@import Parse;
55+
```
5556

5657
#### [Carthage](https://github.com/carthage/carthage)
5758

58-
Add the following line to your Cartfile:
59-
```
60-
github "parse-community/Parse-SDK-iOS-OSX"
61-
```
62-
Run `carthage update`, and you should now have the latest version of Parse SDK in your Carthage folder.
59+
Add the following line to your Cartfile:
60+
```
61+
github "parse-community/Parse-SDK-iOS-OSX"
62+
```
63+
Run `carthage update`, and you should now have the latest version of Parse SDK in your Carthage folder.
6364

64-
This will also compile the ParseTwitterUtils, ParseFacebookUtilsV4 as well as ParseUI frameworks.
65+
This will also compile the ParseTwitterUtils, ParseFacebookUtilsV4 as well as ParseUI frameworks.
6566

6667
#### Compiling for yourself
6768

68-
If you want to manually compile the SDK, clone it locally, and run the following commands in the root directory of the repository:
69+
If you want to manually compile the SDK, clone it locally, and run the following commands in the root directory of the repository:
6970

70-
# To pull in extra dependencies (Bolts and OCMock)
71-
git submodule update --init --recursive
71+
```
72+
# To pull in extra dependencies (Bolts and OCMock)
73+
git submodule update --init --recursive
7274
73-
# To install bundler
74-
gem install bundler
75+
# To install bundler
76+
gem install bundler
7577
76-
# To install all the gems via bundler
77-
bundle install
78+
# To install all the gems via bundler
79+
bundle install
7880
79-
# Build & Package the Frameworks
80-
bundle exec rake package:frameworks
81+
# Build & Package the Frameworks
82+
bundle exec rake package:frameworks
83+
```
8184

82-
Compiled frameworks will be in multiple archives inside the `build/release` folder:
83-
- `Parse-iOS.zip`
84-
- `Parse-macOS.zip`
85-
- `Parse-tvOS.zip`
86-
- `Parse-watchOS.zip`
87-
- `ParseFacebookUtils-iOS.zip`
88-
- `ParseFacebookUtils-tvOS.zip`
89-
- `ParseTwitterUtils-iOS.zip`
90-
- `ParseUI.zip`
85+
Compiled frameworks will be in multiple archives inside the `build/release` folder:
86+
- `Parse-iOS.zip`
87+
- `Parse-macOS.zip`
88+
- `Parse-tvOS.zip`
89+
- `Parse-watchOS.zip`
90+
- `ParseFacebookUtils-iOS.zip`
91+
- `ParseFacebookUtils-tvOS.zip`
92+
- `ParseTwitterUtils-iOS.zip`
93+
- `ParseUI.zip`
9194

9295

9396
#### Using Parse as a sub-project
9497

95-
You can also include parse as a subproject inside of your application if you'd prefer, although we do not recommend this, as it will increase your indexing time significantly. To do so, just drag and drop the Parse.xcodeproj file into your workspace. Note that unit tests will be unavailable if you use Parse like this, as OCMock will be unable to be found.
98+
You can also include parse as a subproject inside of your application if you'd prefer, although we do not recommend this, as it will increase your indexing time significantly. To do so, just drag and drop the Parse.xcodeproj file into your workspace. Note that unit tests will be unavailable if you use Parse like this, as OCMock will be unable to be found.
9699

97100
## How Do I Contribute?
98101

0 commit comments

Comments
 (0)