From 2a63f905a5f36460a4af32a05f24d20425f4e452 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastiano=20Mandal=C3=A0?= Date: Mon, 30 Nov 2020 17:05:02 +0000 Subject: [PATCH] Update README.md --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2529d16..2e8cff5 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,11 @@ The folders Svelto.ECS, Svelto.Tasks and Svelto.Common, where present, are submo ## Svelto is now distributed as Unity Package too [![openupm](https://img.shields.io/npm/v/com.sebaslab.svelto.ecs?label=openupm®istry_uri=https://package.openupm.com)](https://openupm.com/packages/com.sebaslab.svelto.ecs/) -read this article for more information:http://www.sebaslab.com/distributing-svelto-through-openupm/ +read this article for more information:http://www.sebaslab.com/distributing-svelto-through-openupm/ or just install the package that comes from the link https://package-installer.glitch.me/v1/installer/OpenUPM/com.sebaslab.svelto.ecs?registry=https%3A%2F%2Fpackage.openupm.com + +*Note on the System.Runtime.CompilerServices.Unsafe.dll dependency and the bit of a mess that Unity Package Depenendency System is: * + +Unity Package System has a big deficency when it comes to dll dependency solving: two packages cannot point to the same dependency from different sources. Since Unity Collection remove the Unsafe.dll dependency officially (I can't understand this move at all), I had to distribute my own package. This means that if you want to use Svelto from UPM, you will need Svelto unsafe dll to be the only unsafe dll in the project. Otherwise you just download the source code and solve dependencies manually. ## Official Examples