Search Issue Tracker
Fixed in 2021.3.35f1
Fixed in 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a19
Votes
0
Found in
2021.3.22f1
2022.2.12f1
2022.3.0f1
2023.1.0b11
2023.2.0a9
2023.3.0a1
Issue ID
UUM-34899
Regression
No
The project does not build with Linux IL2CPP when executing CLI after building for Windows
Reproduction steps:
1. Open the “Test Project” project folder
2. Change Unity’s version folder path in both “build.sh” and “build2.sh” files
3. Execute “build.sh” through some command prompt (in this case used “Git Bash”)
4. Execute “build2.sh” through some command prompt
Expected result: The Project builds without a failure
Actual result: The command prompt throws an error: “Aborting batchmode due to failure: Failed to build player.”
Reproducible with: 2021.3.22f1, 2022.2.12f1, 2023.1.0b11, 2023.2.0a9
Couldn’t test with: 2020.3.47f1 - Does not build when executing the script
Reproducible on: Windows 10
Note:
- 2021.3 - does not build at all when running the “build2.sh” script
- 2022.2, 2023.1, 2023.2 - when running the “build2.sh” script the second time, the project builds successfully
Comments (1)
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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
ryanjo
Aug 03, 2023 19:57
Problem: The -buildLinux64Player command line argument does not switch the build target to Linux.
Workaround: Add the "-buildTarget Linux" command line option to the Linux build script (build2.sh).