-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Library collision in v1.7 plugin. #146
Comments
Is this something that we'll have to ditch Unity 4 support (or even early 5.x) to fix? (What was wrong with their tagged directories for the plugin platforms? Those worked perfectly fine... arg...) |
This is an easy fix, just checking those boxes for Windows and Android libs. And yes, upgrading to Unity 5 was a prereq, plugins did not have those checkboxes in Unity 4. This replaced the directory structure method of determining the intended platform of plugins, although I think it still uses directory names when upgrading to make a best guess about the bitness. |
Yeah library metadata is new. This shouldn't force a move away from 4, and can probably be addressed with an editor script that post processes package imports. Don't know why they changed it, unless it's to improve scalability with new platforms. |
We've already upgraded to 5, so I'll fix this today. |
Does this mean that Unity 4 is no longer supported? If so, the plugin description on the Asset store should also be changed (this may need a separate ticket). Snippet from the plugin description:
|
The default metatdata for shared libraries in the plugin folder causes a collision when building for Android. This is because the metadata for all shared libraries in the x86 and x86_64 directories are marked for use on all platforms. They should probably only use the Editor and Standalone options.
Repro steps:
The text was updated successfully, but these errors were encountered: