Upgrading an existing project from Unity 2018.2.0f2 to 2018.3.0f2 I get an infinite compilation loop.
I’ve previously moved everything (my code and all 3’rd party assets) to use asmdefs. This is the second large project I’ve done this sort of thing with but the other worked fine.
grepping the logs I see it’s looping the following :
I copied all of these assets into a fresh 2018.3 project and they compile fine.
Searching the forum, I found this thread that suggested two assets might be using SetScriptingDefineSymbolsForGroup() to change the defines in an incompatible way causing the loop (makes sense). grepping I found 2 assets are using those (1 DLL, 1 source based asset). Added both of these to the reproduction-attempt project and still no reproduction. Looking at the actual project’s compile log, I don’t see different defines on subsequent compilations of a given asmdef (e.g. PowerUI compile N compared to N+1).
I also wondered if there could be an asmdef loop that somehow was tripping things up? (though somehow fine in 2018.2?) Wrote a little Python script to parse all the asmdefs and dump a dot file to analyse. Looks fine.
What else can I try? I’ve manually switched the ProjectSettings.asset to use runtime .Net 4 and also tried API .Net 4 but neither made my actual project compilation succeed. When the problem happens, I have to kill Unity from Process Explorer (I’m on Windows). It then reoccurs when I re-open the project = yes every time.
Thanks in advance for any advice/ideas!
