Search Issue Tracker
Fixed
Fixed in 1.8.18
Votes
0
Found in [Package]
1.8.16
Issue ID
BUR-2721
Regression
No
Cannot open input file 'ucrt.lib' with Win-SDK 10.0.26100.0 building for UWP
*Steps to reproduce:*
1. Install [Windows SDK 10.0.26100 |https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/]
2. Create a Unity project with UWP platform extension
3. Install Burst into the project from Package Manager
4. Attempt to build for UWP , Observe Error
*Actual results:*
Build Fails with the following error. Editor logs also attached to this ticket:
{code:java}
Building Library\Bee\artifacts\UWPPlayerBuildProgram\AsyncPluginsFromLinker failed with output:
UnityEditor.Build.BuildFailedException: Burst compiler (1.8.16) failed runningstdout:
Starting 1 library requests
Info: LINK : fatal error LNK1181: cannot open input file 'ucrt.lib'Error: Burst internal compiler error: Burst.Compiler.IL.Aot.AotLinkerException: Non 0 exit code | The native link step failed. Check previous exception in the log - linker command line : "C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.40.33807\bin\Hostx64\arm\link.exe "@C:\\Users\\jackgriffiths\\AppData\\Local\\Temp\\tmpFAC3.tmp""LINK : fatal error LNK1181: cannot open input file 'ucrt.lib'
{code}
*Expected results:*
Build Succeeds - as it does with older versions of the Windows SDK
*Reproducible with versions:*
Windows SDK : 10.0.26100.0
Editor Versions : 2021.3.40f1 (Package version 1.8.16) , 2022.3.37f1 (Package version 1.8.16) & 6000.0.11f1 (Package version 1.8.16)
*Not reproducible with versions:*
Windows SDK : 10.0.22621.0
*Tested on (OS):* Windows Machine (Only applicable as this is Windows SDK)
*Notes:*
* Arose from Forum thread :
[https://forum.unity.com/threads/info-link-fatal-error-lnk1181-cannot-open-input-file-ucrt-lib-hololens-2-build-issue.1604853/#post-9933150]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment