Search Unity

Bug: Imported Windows project can't run, case-sensitivity to blame

Discussion in 'Linux' started by 64746c, Jul 26, 2016.

  1. 64746c

    64746c

    Joined:
    Oct 21, 2007
    Posts:
    181
    I finally fixed a bug that completely stumped me, and I haven't seen anyone else have the same problem, so I figured I should report it here.

    The bug: I cloned my project from a git repo. That project had been worked on using the Windows editor until now. When opening the project in the Linux editor, no errors show, but the message "all compiler errors must be fixed before entering play mode!" shows. Opening the console reveals one error without any message text.

    The fix: The problem was being caused by the assets folder. For whatever reason, the assets folder was stored in the repo as "assets" (with a lowercase A). Renaming that folder to "Assets" (capital A) solved the issue. The reason this was so hard to figure out was that all my assets and scenes still showed up normally, but compiling failed without even being able to say why. (For those Googling this, it showed an exit with status 255).

    Hope this helps someone!

    EDIT: This bug occurred in 5.3.5f1 64-bit Ubuntu.
     
  2. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    One more case sensitivity issue to address - we'll get on it, thanks!