Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
1
Found in
2019.3
2020.1.4f1
2020.2
Issue ID
1275117
Regression
No
Linux IL2CPP build fails when "clang" system package is not installed
How to reproduce:
1. Create and open a new project
2. Press Ctrl+Shift+B to open the "Build Settings" window
3. In the "Build Settings" window press on the "Player Settings..." button
4. In the "Player Settings" panel change the "Scripting Backend" from "Mono" to "IL2CPP"
5. Go back to the "Build Settings" window and make sure the target platform is "Linux"
6. Press the "Build" button to build the project
Expected result: The build gets completed successfully
Actual result: The build fails
Reproducible with: 2019.3.0f5, 2019.4.10f1, 2020.1.6f1, 2020.2.0b3
Could not test with: 2018.4.27f1 (IL2CPP scripting backend not supported on Linux in this stream)
Notes:
1. Reproducible on Ubuntu 18.04
2. Not reproducible on Windows 10
3. Installing the "clang" package seems to resolve the issue, but at least for the user, enabling "Script Debugging" in the build settings still reproduces the bug
-
VertigoJack
Nov 03, 2020 15:49
It seems this isn't a very high priority issue, but we require this to be fixed for our game (we'd like to release builds with IL2CPP on Linux). I've already voted for this issue, is there any way of drawing attention to this?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b5
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b5
Resolution Note (fix version 2020.2):
Fixed in 2020.2.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.21f1