You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing the mono package, I was trying to build a third party project that requires mono and msbuild in order to build. My expectation was that the mono package would also install msbuild, because that's what the official mono installer does.
What happened (include all command output)?
Instead, I encountered a build failure when building the third party project because the Homebrew mono package no longer includes msbuild.
What did you expect to happen?
As per previously resolved issue #29420, "msbuild" is a critical tool for use of modern C#. It is normally found distributed with either the Mono or .NET Core packages.
As such, and in common with the official mono installer from mono-project.com, I'd expect msbuild to be available after installing the mono package.
As a result of issue #29420, support for msbuild was added with PR #29422.
However, it was removed in PR #166109 with this comment stating that it was removed because it was only a dependency of the removed f-sharp executable. However, as several issues have mentioned before, msbuild is shipped with mono and is an essential part of .NET development, so it likely shouldn't have been removed.
You should install the Cask mono-mdk if you want the official mono installer.
MSBuild does not compile on native ARM macOS (which you are on based on brew config) so it was never provided as part of Formula mono.
Upstream needed to re-sync with .NET MSBuild but never got around to it mono/msbuild#435. Upstream is now undergoing some migration to ownership by WineHQ so no idea what is state of project.
For most part, mono formula is only still around for the runtime to be used by dependents (e.g. nuget, paket, etc.). The upstream packaging scripts don't work on ARM macOS and Linux.
Only Intel macOS may still be able to ship everything, but that won't help for your system (unless installing Rosetta, though might as well use Cask instead)
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
After installing the
mono
package, I was trying to build a third party project that requiresmono
andmsbuild
in order to build. My expectation was that themono
package would also installmsbuild
, because that's what the official mono installer does.What happened (include all command output)?
Instead, I encountered a build failure when building the third party project because the Homebrew
mono
package no longer includesmsbuild
.What did you expect to happen?
As per previously resolved issue #29420, "msbuild" is a critical tool for use of modern C#. It is normally found distributed with either the Mono or .NET Core packages.
As such, and in common with the official mono installer from mono-project.com, I'd expect
msbuild
to be available after installing themono
package.As a result of issue #29420, support for
msbuild
was added with PR #29422.However, it was removed in PR #166109 with this comment stating that it was removed because it was only a dependency of the removed f-sharp executable. However, as several issues have mentioned before,
msbuild
is shipped with mono and is an essential part of .NET development, so it likely shouldn't have been removed.Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: