Unity automatically detects plug-insA set of code created outside of Unity that creates functionality in Unity. There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed .NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). More info
See in Glossary for Embedded Linux. When you import plug-ins, Unity creates metadata files for each of those plug-ins. For example, .so
for shared object and shared libraries and .a
for archive files. These metadata files contain the plug-in information, such as the target architecture and platform. The Unity build system refers to these metadata files for tracking which files to copy over during the build process.
You can have several shared libraries with the same name in a project. For example,libFoo.so
for x86_64 and libFoo.so
for arm64 in the same project and Unity detects the correct libFoo.so
and copies it across to the player build depending on the target you are building for.
You can edit these files manually in the Unity Editor. However, you don’t need to manually add plug-ins to the Plugins
folder in your project. Instead, you can place them in special folders located under the project’s Assets/Plugins/EmbeddedLinux
folder in the project directory and Unity automatically detects and sets their platform and architecture for you when importing.
Unity automatically detects plug-ins for Embedded Linux based on the following rules:
Architecture-specific folders - Place plug-ins under Assets/Plugins/EmbeddedLinux/<arch>
, where <arch>
is x86, x86_64, arm, or arm64. Unity copies them only when building an app for the respective target architecture. For example, if you place a plug-in under Assets/Plugins/EmbeddedLinux/x86_64
, Unity copies it to the player build only when building for x86_64.
Plugins with no architecture - Place plug-ins with no architecture under Assets/Plugins/EmbeddedLinux
and ensure that they’re checked for the target architecture through their respective ELF headers and that the appropriate architecture is assigned.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.