Search Issue Tracker
By Design
Votes
1
Found in
2021.3.27f1
2022.3.3f1
2023.1.2f1
2023.2.0a21
Issue ID
UUM-42268
Regression
No
Build fails with console errors when Scripting Backend IL2CPP is selected
Reproduction steps:
1. Open the attached “PluginsTest” project
2. Build the Player (File > Build And Run)
Expected result: The Build is successful
Actual result: The Build fails with “Undefined symbols for architecture arm64:” and “Undefined symbols for architecture x86_64:” console errors
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.2f1, 2023.2.0a21
Reproducible on: macOS Ventura 13.2.1 (M1 Max), macOS 13.4 (Intel)
Note: Not reproducible with Mono Scripting Backend
Comments (2)
-
OLytovch
Jul 11, 2023 11:45
Using the C++ STATIC libs on iOS and Android works fine!
-
OLytovch
Jul 11, 2023 11:41
I just want to clarify that this issue is about using C++ code as a STATIC library in a Unity IL2CPP project. The issue happens on Windows and macOS platforms. The C++ code for Windows is built as *.lib and for macOS built as *.a. The build will fail for such projects.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Unity does not support native static libraries. See https://docs.unity3d.com/Manual/PluginsForDesktop.html for details about native library support.