To build your Linux application, use the following steps:
Configure the required build settings and select one of the following options:
In the Linux file chooser window, select the destination for Unity to place the build.
In the Name field, enter an appropriate name for the build.
Select Save. This starts the build process.
When you build a Unity application on the Linux platform, Unity produces the following files, where ProjectName
is the name of your application:
ProjectName.x86_64
: This is the project executable file for your application. It contains the program entry point that initiates the Unity engine when launched.UnityPlayer.so
: This .so
file contains all the native Unity engine code. It’s signed with the Unity Technologies certificate allowing you to verify that no malicious entities have tampered with your engine code.*.pdb
files: These are symbol files you can use to debug managed (C#) code. Unity copies these files to the build directory if you enable Development BuildA development build includes debug symbols and enables the Profiler. More info*_s.debug
files: These are symbol files you can use to debug native (C/C++) code. Unity copies these files to the build directory if you enable Development Build in the Build Settings window.ProjectName_Data
folder: This folder contains all the data needed to run your application.If you’re using the IL2CPPA Unity-developed scripting back-end which you can use as an alternative to Mono when building projects for some platforms. More info
See in Glossary scripting backendA framework that powers scripting in Unity. Unity supports three different scripting backends depending on target platform: Mono, .NET and IL2CPP. Universal Windows Platform, however, supports only two: .NET and IL2CPP. More info
See in Glossary, your application Player build also includes the following file and folder:
GameAssembly.so
: This .so
file contains all managed (C#) game logic and scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More infoProjectName_BackUpThisFolder_ButDontShipItWithYourGame
folder: This folder contains intermediate files generated during IL2CPP builds that are useful for debugging rather than distribution.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.