koobas.hobune.stream
Using 2 DLLs with the same name
I have a DLL (let's call it A.dll) that depends on another DLL (let's call it B.dll) that has two different versions, one for mobile and one for standalone. I want unity to choose the correct B.dll for the build.
My current file structure for my project is something like
-Assets
-Libs
-A.dll //depends on B.dll
-B.dll //this has it's platform settings set to standalone targets
-MobileLibs
-B.dll //this has it's platform settings set to mobile targets
I've set the target platforms in their respective inspectors to be mutually exclusive so there is no name clash when I run the game in the editor but it always uses the standalone B.dll even when I set the player to a Mobile platform. Even worse, if I delete the standalone version of the B.dll, it can't find the other B.dll that is in the MobileLibs folder.
How can I get this to work? Are there any special folders I need to put these into? I've tried renaming the folder Plugins but that didn't seem to make a difference either.
These are C# libraries built using MonoDevelop if that helps.
It's not really clear what dll you use for the editor. The platform setting only applies to building the game. You also have to choose one dll for in editor use when you want to test your game inside the editor. If your "mobile" version is a specialized version which only works on a mobile device it's obvious that you can't use that one in the editor. It's common that you would use the standalone DLL inside the editor.
Can you include screenshots of the inspector settings of the two DLLs? Or at least be more clear what exact settings you have checked / unchecked for each DLL.
Have a look at this documentation. You will find some specific folders which might help with your problem.
This put me on the right path. What I didn't understand was that when a dll is chosen for use on the Editor platform, it is used for both when you are in play mode and when you are in editor mode. I thought that setting for Editor was only for in Editor mode and the other platforms would be used depending on which build platform you were using.
For anybody seeing this question in the future, having two DLLs with the same name is fine so long as they target different platforms and are in different directories (the above example, in the question describes such a case).
My problem was that I was trying to use a DLL to wrap UnityEngine.Advertisements content. Although it is possible to do so, it is not possible to setup the DLLs in such a way that the target build platform is reflected correctly during Play Mode in the editor. Only precompiler macros can properly do that but they are not effective in DLLs.
I am trying to use two different $$anonymous$$ongoDB.Driver and $$anonymous$$ongoDB.Bson drivers. One is for 3.5 the other is 4.x but it doesn't seem to want to let me do that?
Unity will assign the precomplier directive UNITY_EDITOR, when compiling for the editor, (including the editor-"player") When compiling for a final project/platform, UNITY_EDITOR is NOT defined.
So...
#if UNITY_EDITOR
using a.dll // used when compiled for the editor (what you get when you hit play)
#else
using b.dll // used when compiled for the runtime project.
#endif
(Both dll's would live in your regular asset folder.)
EDIT: I should also mention, that each target option has a place where you can specify your OWN preprocessor pragma. You can assign each target a different pragma, and use the pattern shown above, replacing with your own pragmas.
I THINK you have that part already understood though, and it sound like you want to know how to compile the DLL itself. THAT answer is really ugly. Here is how I did it: http://answers.unity3d.com/questions/1347169/how-to-conditional-use-of-unityeditor-in-dll.html (I really hope someone posts a better way!)
Uhm i think that the two DLLs have actually the same namespaces. It's just two different implementations. At least that's what i understood from the question.
ps: There's not really any other way in your case as pre-processor tags are only read before the actual compilation. Since your DLL is already in compiled form the tags doesn't exist anymore. So you would have to create two seperate versions. Even all of the Unity extensions have seperate Editor and runtime versions. Just look into "Unity/Editor//Data/UnityExtensions/Unity/" The new GUI system as well as the networking library have a seperate editor and standalone version.
The "UnityHoloLens" extension also seems to have a seperate Editor, Runtime and RuntimeEditor version.
"Even all of the Unity extensions have seperate Editor and runtime versions" How does it know which one to use for a given compilation? I would suspect some difference in the "command line" issued to the compiler. How ever it is done can we somehow "tap" into that?
Well, extensions of course work a bit different as they are handled by the editor in a different way. However in general you should be able to use the plugin inspector to specify for which platforms an assembly should be used. Though as the question was written it seems that what he's doing but we don't know his actually settings on the two B assemblies. That's why i posted my comment on the question.
There are also special folders which Unity recognises for different platforms. All can be read on this page:
To make transition easier from earlier Unity versions, Unity will try to set default plugins settings, depending on the folder where the plugin is located.
So the plugin inspector settings should actually be enough. Though many people do not recognise the editor as seperate platform.
