[Pkg-mono-devel] dh_clideps: Warning: Could not resolve moduleref: libKitware.mummy.Runtime.Unmanaged.so for: Kitware.mummy.Runtime.dll!

Jo Shields directhex at apebox.org
Sat Feb 19 10:55:10 UTC 2011


On Thu, 2011-02-17 at 21:35 +0100, Mathieu Malaterre wrote:
> Dear all,
> 
>   I am trying to package the mummy package. My attempt can be found at:
> 
> http://mentors.debian.net/debian/pool/main/m/mummy/
> 
>   During the compilation I always get the following warning:
> 
> dh_clideps: Warning: Could not resolve moduleref:
> libKitware.mummy.Runtime.Unmanaged.so for: Kitware.mummy.Runtime.dll!
> 
> I do not understand what is missing in my package.
> 
> Could some C# guru have a peak at my work ?

It's not a problem - it's a reasonably common warning when putting CLI
stuff and C stuff in the same package without using a dllmap. You'll see
similar errors in the build logs for things like Banshee.

There are a few other packaging errors and oddities though.

Firstly, you identify libmummy-1.0-cil as " CLI bindings to the Mummy
library" - but the package isn't depending on anything identifying
itself as "the Mummy library", so it's not really a binding.

Secondly, if it's a lib that should be used for development (i.e. a
binding), then there should be a .pc file in a -cil-dev package. If it's
not for that, then it's not clear to me how one would "use" the package.

Thirdly, package install locations should reflect the assembly name (and
not contain a spurious dash, much like a C soname), so
Kitware.mummy.Runtime.dll lives
in /usr/lib/cli/Kitware.mummy.Runtime-1.0/ - assuming it's a GAC
library, which leads on to point 4:

Fourthly, if a lib is a GAC lib, it should be in a version-numbered
package and go in /usr/lib/cli (in this case,
libkitware-mummy-runtime1.0-cil) - and include a .installcligac file to
specify that the lib should go into the GAC where apps can consume it.
In this case, the lib isn't installing to the GAC, so I'm not sure if it
should follow the GAC rules or is expected to go into the GAC - if not,
the package name should not include a version number, the install
location should just be in /usr/lib/ not /usr/lib/cli, and a valid
pkg-config file becomes all the more important




More information about the Pkg-mono-devel mailing list