|
We've just upgraded our Unity installed base from 2.6 to 3.0. When we were running 2.6, the project would build fine using our automated build system. Under 3.0 the project fails with this error: Error building Player: Extracting referenced dlls failed. UnityEditor.HostView:OnGUI() No new dlls have been added to the project since we were using 2.6. I found references to this problem by other people: Anybody know what's going on here? Why did it work fine in 2.6 but not in 3.0? We also see this error: ArgumentException: The Assembly UnityEditor is referenced by Path. But the dll is not allowed to be included or could not be found.
UnityEditor.AssemblyHelper.AddReferencedAssembliesRecurse (System.String assemblyPath, System.Collections.Generic.List One thing I noticed about the second error is "Path". We're using AngryAnt's Path library. Then I found this question. I think we may be on to something...
(comments are locked)
|
|
Path 1.0 is not Unity 3 compatible. I'm currently working on a 1.1 release which will address this and many other things. Some background: Unity 2.x allowed assemblies to link to UnityEditor and still be compiled in with everything else on build time as long as it didn't try to invoke anything in UnityEditor. Unity 3 is more strict and requires a complete split between UnityEditor code and UnityEngine code. Thanks for letting us know. We came up with a workaround.
Oct 18 '10 at 01:12 PM
Josh 4
(comments are locked)
|
|
This is most likely due to the much more restrictive handling of Mono in Unity 3. There's now different profiles and not all of the profiles support all the Mono features. In particular, Web players can only use a limited set of Mono features which might explain the behavior. We're only building for standalone Windows and OS X. Are the restrictions documented somewhere? What are the different profiles and where can I find out more? Eventually we want to release this or a future product for the webplayer as well. Do you have any good pointers to information on these restrictions for each deployment scenario?
Oct 08 '10 at 12:40 PM
Ben 2
One of the issues turned out to be that the Path library included classes that referenced the UnityEditor package and we did not have it in the Editor folder. I work with Ben although he would not admit that ;-). Apparently this offends 3.0 more than 2.6.1 . Moving it there caused other issues for us so we wound up getting the source for that and splitting all the stuff into the correct compile phase in our project. I think that introduced more errors which I think he has linked in a comment above.
Oct 11 '10 at 12:27 AM
raypendergraph
(comments are locked)
|
|
You can try to change API Compatibility Level: to .Net 2.0. choose Edit->Project Settings->Player, then follow this link http://unity3d.com/support/documentation/Components/class-PlayerSettings.html Helped me with building..
(comments are locked)
|
|
Is anyone found solution for that. I'm experiencing same problem with UniLOD on Unity 3.1
(comments are locked)
|
One, strange solution I have found that sometimes works is to create a duplicate of your project and try building that one. It doesn't always work, but it seems that sometimes linkage gets lost to the project folder.
An interesting idea but I don't want to modify our build system to make an unnecessary copy of the project, especially if its only works some of the time.
I should add, we're trying to build both mac and windows versions of the project. We are not building for the webplayer.
We're also getting this error:
Thread::CurrentThreadIsMainThread()
which may or may not be related.
Are you also building Web players? Can you build all the targets you have in the build-script also directly from the Editor?