diff --git a/docs/linking-libraries.html b/docs/linking-libraries.html index 442efcc453f..7d5542a6de9 100644 --- a/docs/linking-libraries.html +++ b/docs/linking-libraries.html @@ -2,7 +2,7 @@ all those features would impact the binary size... But we still want to make it easy to add these features whenever you need them.
With that in mind we exposed many of these features as independent static libraries.
For most of the libs it will be as simple as dragging two files, sometimes a third step will be necessary, but no more than that.
All the libraries we ship with React Native live on the Libraries folder in
-the root of the repository. Some of them are pure JavaScript, and you just need
+the root of the repository. Some of them are pure JavaScript, and you only need
to require it. Other libraries also rely on some native code, in that case
you'll have to add these files to your app, otherwise the app will throw an
error as soon as you try to use the library.
If the library has native code, there must be a .xcodeproj file inside it's
@@ -10,8 +10,8 @@ folder.
Drag this file to your project on Xcode (usually under the Libaries group
on Xcode);

Click on your main project file (the one that represents the .xcodeproj)
select Build Phases and drag the static library from the Products folder
-inside the Library you are importing to Link Binary With Libraries

Not every library will need this step, what you need to consider is:
Do I need to know the contents of the library at compile time?
What that means is, are you using this library on the native site or just in -JavaScript? If you are just using it in JavaScript, you are good to go!
This step is not necessary for libraries that we ship with React Native with the
+inside the Library you are importing to Link Binary With Libraries

Not every library will need this step, what you need to consider is:
Do I need to know the contents of the library at compile time?
What that means is, are you using this library on the native side or only in +JavaScript? If you are only using it in JavaScript, you are good to go!
This step is not necessary for libraries that we ship with React Native with the
exception of PushNotificationIOS and LinkingIOS.
In the case of the PushNotificationIOS for example, you have to call a method
on the library from your AppDelegate every time a new push notifiation is
received.
For that we need to know the library's headers. To achieve that you have to go