You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the builder, it ended up giving me the following error
my project has 4 assambly defined Application, Infrastrucubre, Domain, Presentation with its own .asmdef
-----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp-Editor.dll
Microsoft (R) Visual C# Compiler version 3.5.0-dev-20359-01 (8da8ba0c)
Copyright (C) Microsoft Corporation. All rights reserved.
Assets/Editor/Editor/Versioning/Git.cs(107,35): error CS0234: The type or namespace name 'dataPath' does not exist in the namespace 'Application' (are you missing an assembly reference?)
-----EndCompilerOutput---------------
- Finished script compilation in 56.329191 seconds
Assets/Editor/Editor/Versioning/Git.cs(107,35): error CS0234: The type or namespace name 'dataPath' does not exist in the namespace 'Application' (are you missing an assembly reference?)
AssetDatabase: script compilation time: 57.937374s
Scripts have compiler errors.
Aborting batchmode due to failure:
Scripts have compiler errors.
AcceleratorClientConnectionCallback - disconnected - :0
/home/bokken/buildslave/unity/build/PlatformDependent/Linux/External/baselib/builds/Include/C/Baselib_ThreadLocalStorage.inl.h(13): Assertion failed (rc == 0)
Caught fatal signal - signo:5 code:128 errno:0 addr:(nil)
Build failed, with exit code 1
Looks like a name conflict where your Application namespace is conflicting with UnityEngine.Application.
I raised a PR to add UnityEngine to our build script, which would fix the issue there.
However, it's entirely possible that there will be another name conflict somewhere else.
Sorry if my English is not good
When running the builder, it ended up giving me the following error
my project has 4 assambly defined Application, Infrastrucubre, Domain, Presentation with its own .asmdef
my .yaml
logs_12.zip
The text was updated successfully, but these errors were encountered: