-
Notifications
You must be signed in to change notification settings - Fork 515
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
Metal compiler build failures are not displayed by dotnet build at minimal verbosity #21437
Comments
Ideally, I'd expect that the build error should be shown in the "PROBLEMS" tab of VS Code |
Try to run this in the terminal, it's possible a environment issue. |
I would love to see it fixed too! |
@Search2Code the attached output is from the terminal, the results are the same in VS Code too. AFAIK everyone on my team is affected by the same issue. |
rolfbjarne
added a commit
that referenced
this issue
Oct 15, 2024
This has a few advantages: * We simplify and unify more of our code. * We have more control over the error reporting / logging behavior. Additionally: * Use 'xcrun' to invoke 'metal' and 'metallib' (partial fix for #3931). * Allow for overriding the path to the command-line tool in question. * Add support for cancellation. * Fix nullability. Fixes #21437.
Thanks for the report - fix is in progress. |
rolfbjarne
added a commit
that referenced
this issue
Oct 16, 2024
This has a few advantages: * We simplify and unify more of our code. * We have more control over the error reporting / logging behavior. Additionally: * Allow for overriding the path to the command-line tool in question. * Add support for cancellation. Fixes #21437.
haritha-mohan
pushed a commit
that referenced
this issue
Oct 19, 2024
…. (#21439) This has a few advantages: * We simplify and unify more of our code. * We have more control over the error reporting / logging behavior. Additionally: * Use 'xcrun' to invoke 'metal' and 'metallib' (partial fix for #3931). * Allow for overriding the path to the command-line tool in question. * Add support for cancellation. * Fix nullability. Fixes #21437.
rolfbjarne
added a commit
that referenced
this issue
Oct 22, 2024
This has a few advantages: * We simplify and unify more of our code. * We have more control over the error reporting / logging behavior. Additionally: * Allow for overriding the path to the command-line tool in question. * Add support for cancellation. Fixes #21437.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Apple platform
iOS, Mac Catalyst
Framework version
net8.0-, net9.0-
Affected platform version
8.0.403, 9.0.100-rc.2.24474.11
Description
dotnet build does not show the reason compiling a Metal file failed, it only reports that metal exited with an error code:
But the error is not useful without including the output from the metal compiler:
Steps to Reproduce
git clone https://github.com/jeremy-visionaid/MacCatalystApp1
Did you find any workaround?
dotnet build -v:normal
Build logs
No response
The text was updated successfully, but these errors were encountered: