-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Cannot build latest master #16656
Comments
Running fine for me. Can you do all the cleaning rituals and try again? |
@ErikEJ Are you still having issues? Anything we can help with? |
I had similar issue on a second machine, and it was because I did not have the latest preview 6 SDK installed (from June 12), but an earlier one. I will close this, wising there was a way to have a check of some sort at the start of the build process, it took me a few attempts to figure out. But I guess it is all a point in time issue. |
Did all the cleaning, installed the correct SDK, build still failing with same error !? |
I a running from a fork and has a origin and upstream remotes (unlike you guys do) - I wonder if this is related to this recent bug fix, which is not in the package currently used by EF Core build: dotnet/sourcelink@855afb5 (EF Core build uses the previous package version: 1.0.0-beta2-19351-01 ) |
OK, it turns out this piece of code assumes that git.exe is in the PATH - and of course that is not the case on either of my machines! It seems like a steep requirement for a build to succeed - but at least a more helpful error message would be useful! After adding git.exe to the path, the build runs! 😄 |
I have created an issue in the sourcelink repo |
Thanks for getting to the bottom of this @ErikEJ! |
Is this something that should be added to the wiki? (Building the code wiki page) |
This is a bug. Source Link does not require git.exe isntalled on the machine. It's already been fixed: dotnet/sourcelink#337, included in Arcade via dotnet/arcade#3302. |
Running command line build of latest master fails with:
The text was updated successfully, but these errors were encountered: