-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiler error when importing via UPM #38
Comments
upm package does not include managed dlls. |
There are UPM packages that provide DLLS, though. Is there any reason those DLLs can't be split off into separate packages that ZString uses as a dependency? |
Other packages that using System.Memory etc(ZLogger, MessagePack-CSharp, etc) are exists. |
Those are all your packages, right? So can't you make all of them depend on these DLLs (or just the ones that they need at least)? Given how popular your packages are, I bet if you wrapped |
These packages are certainly under my control, but System.* itself is used by others, so there is always the possibility of conflicts. |
Dang. Is there any reason you couldn't prepare a package containing a version of these libraries that's known to work with your packages but is technically an optional dependency? Right now ZString and ZLogger are the only libraries I use that require |
i recommend using the samples of the package just to import the dlls |
Yeah that's what I do now, but I'd rather keep dependencies out of my git repo where possible. |
merged, thanks all. |
When I import ZString with the following minimal
manifest.json
......I get this set of compiler errors:
There are many similar compiler errors as well. This occurs on Unity 2020.2.1f1 on Windows 10.
The text was updated successfully, but these errors were encountered: