


I saw in csound that it uses libsndfile and boost and several others. Otherwise the host machine that downloads the package might not have the dlls needed. You still have to add any dependencies the C++ lib itself is using. On UnityEditor 2018.2.6f1 is not working neither on the Editor nor in build (DllNotFoundException), wherever I place the dll ( Assets/Plugins, Package/Scripts/Plugins, Package/Scripts) and that sounds really strange (nobody ever noticed that?), I'll look for some bug report about Plugins on this version.Ĭould the problem reside in the dll in some way?Ĭlick to expand.Could be that Unity links to some stuff by default. Plugins: Failed to load 'C:/Path/To/Project/Packages/PackageName/Scripts/Runtime/Win64/myLib.dll' because one or more of its dependencies could not be loaded. Same behaviour on UnityEditor 2019.2.18f1,Įxcept that I can see 6 lines like these before the DllNotFoundException: I tried creating the Visual Studio projects with 3 cases:Ī Plugins folder is created inside vsproject/build/bin/AppName_Data, the dll is there and it worksĪ Plugins folder is created inside vsproject/build/bin/AppName_Data, the dll is there and it works, doesn't work on Editor (DllNotFoundException) I'm on the latest UnityEditor ( 2019.3.9f1). I did some other tests, sounds like a bug of the editor, the build is working! Maybe this is whats wrong with my plugins.īut if so, why is it working when the package is in a different location? does Plugins work the same with assembly files?ĭo I also have to reference the assembly file in order to work with them? I mentioned the package path because that's the only difference, when I download the package from the registry, unity saves it in the Library folder, and the files are marked as "Read Only"Ī quick question. Now, in the new project, the package is downloaded fine, but the plugins are not loaded, the resources cant be accessed So I publish my package to an npm repository, and I use a new project to download the package.

Testing this for android platform, but it reacts the same when I tried for windows I'm using unity 2019.3 (but also test on 2019.2) working on windows machine
