diff options
| author |  spomorski <spomorski@google.com> | 2017-10-26 17:21:55 +0200 |
|---|---|---|
| committer |  Dmitry Lomov <dslomov@google.com> | 2017-10-27 16:29:24 +0200 |
| commit | 24ffb952e820554f4780bab073fcdbf9a755149f (patch) | |
| tree | 47f5d111eea67a296cf4da74bbeb4ee0fcc02ab3 /site | |
| parent | 9923fec9c5203e0b10c1bc4b67321c9ec0ba6da9 (diff) | |
Fix link and formatting.
PiperOrigin-RevId: 173540551
Diffstat (limited to 'site')
| -rw-r--r-- | site/_layouts/documentation.html | 2 | ||||
| -rw-r--r-- | site/docs/migrate-cocoapods.md | 14 |
2 files changed, 8 insertions, 8 deletions
diff --git a/site/_layouts/documentation.html b/site/_layouts/documentation.html index bec68a5c31..ac7c98dd87 100644 --- a/site/_layouts/documentation.html +++ b/site/_layouts/documentation.html @@ -169,7 +169,7 @@ nav: docs <h3>Experimental</h3> <ul class="sidebar-nav"> <li><a href="/versions/{{ site.version }}/experimental.html">About experimental features</a></li> - <li><a href="/versions/{{ site.version }}/migrate-cocoapopds.html">Converting CocoaPods dependencies</a></li> + <li><a href="/versions/{{ site.version }}/migrate-cocoapods.html">Converting CocoaPods dependencies</a></li> </ul> </nav> </div> diff --git a/site/docs/migrate-cocoapods.md b/site/docs/migrate-cocoapods.md index 0d2679958d..f046f62061 100644 --- a/site/docs/migrate-cocoapods.md +++ b/site/docs/migrate-cocoapods.md @@ -22,19 +22,19 @@ If you're using CocoaPods, you need to: 3. Document the dependency tree, including the hierarchy of the `Podspecs`, resource URLs, filenames, and version numbers. -## Converting a Podspec to a Bazel package +## Converting a `Podspec` to a Bazel package -To convert a Podspec dependency to a Bazel package, do the following: +To convert a `Podspec` dependency to a Bazel package, do the following: -1. Download each Podspec and decompress it into its own directory within the - Bazel workspace. All Podspecs must reside within the same Bazel workspace for - Tulsi to be aware of them for inclusion in the Xcode project. +1. Download each `Podspec` and decompress it into its own directory within the + Bazel workspace. All `Podspec`s must reside within the same Bazel workspace + for Tulsi to be aware of them for inclusion in the Xcode project. -2. Within the Podspec directory, create a `BUILD` file that specifies the +2. Within the `Podspec` directory, create a `BUILD` file that specifies the library target(s) referencing the source and header files on which your project depends. -3. Based on your project's dependency tree, add the Podspec target(s) as +3. Based on your project's dependency tree, add the `Podspec`s target(s) as dependencies to the appropriate targets in the project's `BUILD` file(s). 4. In the project's `BUILD` files, configure package visibility as desired. |