mdtool errors not displaying?

Unity Engine
1

Hello everyone.

I am attempting to build my project via the command line, and everything seems to be moving along, but when I build the project, I have errors but no detailed error messages.

For example, I use this command (broken up for readability):

/Applications/Unity/MonoDevelop.app/Contents/Frameworks/Mono.framework/Commands/mono 
/Applications/Unity/MonoDevelop.app/Contents/MacOS/lib/monodevelop/bin/mdtool.exe 
-v build 
-c:smile:ebug 
~/unity_project/unity_project.sln

And the build process starts but at the end, all I get for error details is

Unrecognized compiler output: 1 warning(s).
Unrecognized compiler output: 1 error(s).
      Build complete -- 1 error, 1 warning

I don’t get the info on the actual errors or warnings.

I have verbose enabled and I checked stderr and nothing seems to be reported there either so I’m at a bit of a loss as to where MonoDevelop is picking up the actual error messages from (or where mdtool would be reporting them).

And of course

/Applications/Unity/Unity.app/Contents/MacOS/Unity -batchmode -logFile -projectPath ~/unity_project -quit

gives me full details, as does the MonoDevelop GUI.

Any suggestions?

2

BTW, this looks to be specific to Boo files, with what looksl ike the offending code coming from

I dunno… did the boo compiler change recently? Doesn’t really make too much sense since MonoDevelop still picks up the errors just fine…

3

So, I figured this out, in a way.

The issue is that /Applications/Unity/MonoDevelop.app/Contents/MacOS/lib/monodevelop/AddIns/BackendBindings/Boo/Boo.MonoDevelop.dll isn’t outputting the error messages for Boo. You can see in the code boo-md-addins/src/UnityScript.MonoDevelop/ProjectModel/UnityScriptCompiler.boo at master · bamboo/boo-md-addins · GitHub that’s going on, in ParseBuildResult—the messages are being provided to MonoDevelop via the BuildResult object, but, they are not printed out to the console, which is what we want if we are going to use flycheck/flymake!

I had a lot of trouble compiling boo-md-addons from the github repo. After struggling with that it occured to me:

Hell, just take the DLL you have now and edit it directly to put in a print statement!

So, I grabbed RedGate’s .NET Reflector and an addon called Reflexil. With those two tools I was able to examine the IL for the DLL and add a print statement at what would be essentially line 103 in the above boo code. Saved the patched DLL, plopped it where the old one was, and everything worked.

:stuck_out_tongue: