C# suddenly no longer building on Linux
This is just weird. The other day, Unity was working beautifully. I have made no knowing changes since then; but now no scripts will compile and run. I get no printed messages, no errors, no warnings; and so you're aware of the extent of it, I have a trial component that just contains this (to the letter:)
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class PrintBSToBeSure : MonoBehaviour {
// Use this for initialization
void Start () {
Debug.Log("Starting");
}
// Update is called once per frame
void Update () {
Debug.Log("BS");
}
}
Absolutely nothing happens when it is attached to a GameObject.
I have also attempted to start a brand new project, and implement the script in it—same result. Interestingly enough, asset packages (like Unity Standard Assets) still run fine. I can also highlight that I have nothing down in the console window other than "Clear on Play". I used to use Atom for coding, but switched to MonoDevelop (internal) to be sure; no changes. Attempting to build within MonoDevelop gives me the warning "Reference System.XML not resolved" followed by 31 errors involving a System.* class not being found, as though it isn't even finding Mono, which is again weird because I know I have it—I checked. That's Mono 4.0 with all of the toppings. I am using .NET Framework 4.1.
Unity version is 2017.1.1x, on Linux Mint; my next step is to check for updates and hope for a magical fix, or start working on Windows again (which is extremely inconvenient as all of my media development tools are Linux-based).
Can anyone give me a solid signal as to what might be wrong?
—————
Note: I've noticed that the two trailing projects, Assembly-CSharp-Editor-firstpass and Assembly-CSharp-firstpass, were encountering the same error. Having set them all to use the most updated version of Mono, they appear to be finding references now, which is good. However, I still see no modifications on the behavior of my project.
Now that I'm making headway I'm likely to keep digging, and will post any discoveries here. If I'm overlooking an elephant, though, I'd love to hear it.
Your answer
Follow this Question
Related Questions
Error with Instantiate after build 0 Answers
ProBuilder script standalone build exceptions 0 Answers
Is DateTime working on iOS? 0 Answers
Adding additional C# scripts after build (Android, iOS) 1 Answer
Unity won't build my scripts 0 Answers