Search Unity

Don't require meta files in packages where they aren't needed

Discussion in 'Package Manager' started by thefallengamesstudio, Feb 7, 2020.

  1. thefallengamesstudio


    Mar 7, 2016

    I'm personally forced to transition a common DLL used both on the server and the client to a package because it previously referenced UnityEngine.UI, which is not available anymore.

    I compile the common DLL as usual referencing an old UnityEngine.UI.dll for the server (I need it on the server indirectly - long story), and make the common C# project folder have the structure of a package, i.e. replacing "bin" and "obj" with "bin~" and "obj~" (so they'll be ignored), adding package.json etc. and linking that package into the unity project where my client code resides.

    Currently I'm linking its folder as an embedded package (via symlink to the actual common C# project), which automatically creates the meta files for me, but what I'd like is to not have any meta files inside the package, where they're not needed (and keep the common project clean). For ex., I have no MonoBehaviours in it, so I don't see why meta files would be needed.

    A friendly solution would be to allow meta files if they already exist, but not require them for non-reference-able .cs files.

    @okcompute_unity, @maximeb_unity, do you have any input on this?