-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BDN boilerplate project is not strong named for WASM AOT #2026
Comments
This has the look of some check being enabled in the SDK that wasn't before. I will try to find out what it is and how to disable or satisfy it. |
That looks like we're running the AOT compiler on a native .dll for some reason. |
This is the related/known issue dotnet/runtime#46856 The best thing to do would be to exclude this KernelTraceControl.dll from the wasm (or really any non-Windows) build |
So it seems like the issue is that AOT compiler is trying to compile a native DLL. I am not sure exactly why this is coming up now; it is just trying to compile everything the ends up in the publish directory. Maybe a change in BDN added this? Discussing with @radical, it seems like the AOT compiler should just skip any native assemblies it encounters, emitting a warning when doing so. I will make that change. I think I can do this by using PEReader.HasMetadata around here: https://github.com/dotnet/runtime/blob/cf796613157e5d028ab292d4312c321b97fa94ed/src/tasks/AotCompilerTask/MonoAOTCompiler.cs#L879-L882 |
Actually, the quickest solution might be to jsut fitler out that DLL from WasmAssembliesToBundle here: https://github.com/dotnet/BenchmarkDotNet/blob/38b99b9a038fb065312978995f2cb9223ad88417/src/BenchmarkDotNet/Templates/WasmAotCsProj.txt#L41 The proper solution belongs in the SDK somewhere, but may take time to work out. |
wasm aot run is green now. |
Looks like we have either stopped strong name signing, or never did and it was not an issue, the BDN boilerplate project. This is now causing issues in WASM AOT, where it seems we require a strong name.
The text was updated successfully, but these errors were encountered: