@@ -36,16 +36,16 @@ dependencies on Android) provides solutions for each of these problems.
36
36
## Android Dependency Management
37
37
38
38
The * Android Resolver* component of this plugin will download and integrate
39
- Android library dependencies and handle any conflicts between plugins that share
39
+ Android library dependencies and handle any conflicts between plugins that share
40
40
the same dependencies.
41
41
42
- Without the Android Resolver, typically Unity plugins bundle their AAR and
42
+ Without the Android Resolver, typically Unity plugins bundle their AAR and
43
43
JAR dependencies, e.g. a Unity plugin ` SomePlugin ` that requires the Google
44
44
Play Games Android library would redistribute the library and its transitive
45
45
dependencies in the folder ` SomePlugin/Android/ ` . When a user imports
46
46
` SomeOtherPlugin ` that includes the same libraries (potentially at different
47
47
versions) in ` SomeOtherPlugin/Android/ ` , the developer using ` SomePlugin ` and
48
- ` SomeOtherPlugin ` will see an error when building for Android that can be hard
48
+ ` SomeOtherPlugin ` will see an error when building for Android that can be hard
49
49
to interpret.
50
50
51
51
Using the Android Resolver to manage Android library dependencies:
@@ -102,7 +102,7 @@ always be the version activated in a developer's Unity project.
102
102
103
103
Plugin creators are encouraged to adopt this library to ease integration for
104
104
their customers. For more information about integrating Play Services Resolver
105
- into your own plugin, see the [ Plugin Redistribution] ( #plugin-redistribution )
105
+ into your own plugin, see the [ Plugin Redistribution] ( #plugin-redistribution )
106
106
section of this document.
107
107
108
108
# Requirements
@@ -115,34 +115,34 @@ depends upon the `PluginImporter` UnityEditor API.
115
115
116
116
# Getting Started
117
117
118
- Before you import the Play Services Resolver into your plugin project, you first
118
+ Before you import the Play Services Resolver into your plugin project, you first
119
119
need to consider whether you intend to * redistribute* Play Services Resolver
120
120
along with your own plugin.
121
121
122
- Redistributing the ` Play Services Resolver ` inside your own plugin will ease
122
+ Redistributing the ` Play Services Resolver ` inside your own plugin will ease
123
123
the integration process for your users, by resolving dependency conflicts
124
124
between your plugin and other plugins in a user's project.
125
125
126
126
If you wish to redistribute the ` Play Services Resolver ` inside your plugin,
127
- you ** must** follow these steps when importing the
127
+ you ** must** follow these steps when importing the
128
128
` play-services-resolver-*.unitypackage ` , and when exporting your own plugin
129
129
package:
130
130
131
131
1 . Import the ` play-services-resolver-*.unitypackage ` into your plugin
132
- project by
132
+ project by
133
133
[ running Unity from the command line] ( https://docs.unity3d.com/Manual/CommandLineArguments.html ) , ensuring that
134
134
you add the ` -gvh_disable ` option.
135
- 1 . Export your plugin by [ running Unity from the command line] ( https://docs.unity3d.com/Manual/CommandLineArguments.html ) , ensuring that
135
+ 1 . Export your plugin by [ running Unity from the command line] ( https://docs.unity3d.com/Manual/CommandLineArguments.html ) , ensuring that
136
136
you:
137
137
- Include the contents of the ` Assets/PlayServicesResolver ` directory.
138
138
- Add the ` -gvh_disable ` option.
139
139
140
- You ** must** specify the ` -gvh_disable ` option in order for the Version
140
+ You ** must** specify the ` -gvh_disable ` option in order for the Version
141
141
Handler to work correctly!
142
142
143
143
For example, the following command will import the
144
- ` play-services-resolver-1.2.46.0.unitypackage ` into the project
145
- ` MyPluginProject ` and export the entire Assets folder to
144
+ ` play-services-resolver-1.2.46.0.unitypackage ` into the project
145
+ ` MyPluginProject ` and export the entire Assets folder to
146
146
` MyPlugin.unitypackage ` :
147
147
148
148
```
@@ -157,12 +157,12 @@ Unity -gvh_disable \
157
157
## Background
158
158
159
159
The * Version Handler* component relies upon deferring the load of editor DLLs
160
- so that it can run first and determine the latest version of a plugin component
160
+ so that it can run first and determine the latest version of a plugin component
161
161
to activate. The build of the ` Play Services Resolver ` plugin has Unity asset
162
162
metadata that is configured so that the editor components are not
163
163
initially enabled when it's imported into a Unity project. To maintain this
164
164
configuration when importing the ` Play Services Resolver ` .unitypackage
165
- into a Unity plugin project, you * must* specify the command line option
165
+ into a Unity plugin project, you * must* specify the command line option
166
166
` -gvh_disable ` which will prevent the Version Handler component from running and
167
167
changing the Unity asset metadata.
168
168
@@ -172,7 +172,7 @@ The Android Resolver copies specified dependencies from local or remote Maven
172
172
repositories into the Unity project when a user selects Android as the build
173
173
target in the Unity editor.
174
174
175
- 1 . Add the ` play-services-resolver-*.unitypackage ` to your plugin
175
+ 1 . Add the ` play-services-resolver-*.unitypackage ` to your plugin
176
176
project (assuming you are developing a plugin). If you are redistributing
177
177
the Play Services Resolver with your plugin, you ** must** follow the
178
178
import steps in the [ Getting Started] ( #getting-started ) section!
@@ -294,6 +294,13 @@ The Android Resolver creates the
294
294
of resolved dependencies in a project. This is used by the auto-resolution
295
295
process to only run the expensive resolution process when necessary.
296
296
297
+ ## Displaying Dependencies
298
+
299
+ It's possible to display the set of dependencies the Android Resolver
300
+ would download and process in your project via the
301
+ ` Assets > Play Services Resolver > Android Resolver > Display Libraries ` menu
302
+ item.
303
+
297
304
# iOS Resolver Usage
298
305
299
306
The iOS resolver component of this plugin manages
@@ -303,7 +310,7 @@ to the Xcode project exported by Unity.
303
310
304
311
Dependencies for iOS are added by referring to CocoaPods.
305
312
306
- 1 . Add the ` play-services-resolver-*.unitypackage ` to your plugin
313
+ 1 . Add the ` play-services-resolver-*.unitypackage ` to your plugin
307
314
project (assuming you are developing a plugin). If you are redistributing
308
315
the Play Services Resolver with your plugin, you ** must** follow the
309
316
import steps in the [ Getting Started] ( #getting-started ) section!
@@ -360,7 +367,7 @@ Unity plugins can be managed by the Version Handler using the following steps:
360
367
1 . Optional: If your plugin is included in other Unity plugins, you should
361
368
add the version number to each filename and change the GUID of each asset.
362
369
This allows multiple versions of your plugin to be imported into a Unity
363
- project, with the Version Handler component activating only the most
370
+ project, with the Version Handler component activating only the most
364
371
recent version.
365
372
1 . Create a manifest text file named ` MY_UNIQUE_PLUGIN_NAME_VERSION.txt `
366
373
that lists all the files in your plugin relative to the project root.
0 commit comments