[MonoDevelop] Autotools plugin.

Scott Ellington scottell.lists at gmail.com
Mon Aug 14 10:33:05 EDT 2006


On Mon, 2006-08-14 at 12:28 -0400, Miguel de Icaza wrote:
> Am not sur ewhat is this "Libraries" variable, is this the same as the
> output for --libs?

The --libs output provides something like "-r:mydll.dll -r:other.dll".
For unstable API libraries (i.e. ones that should not go in the GAC),
the guidelines say to use an additional variable 'Libraries' in the pc
file.  For the above example, the value would be "mydll.dll other.dll". 

The consumers can then use this variable to copy over the dlls into the
ouput directory for running the app.  The problem is that the --libs
output is recursive, providing all the dependencies of dependencies and
so forth, while the 'Libraries' output will only bring back the toplevel
package output.

I'm not sure how to resolve this.  There may be a way within pkg-config
I am unaware of.

> I think that we should have all the dependencies listed in the -r:
> parameters that is generated by the pkg-config file.
> In addition, I believe that when generating the tarball, we should ship
> the binary DLLs as a fallback, but always try to use a system version if
> it is available (just to appease the Debian crowd which does not like
> using binaries shipped with a tarball).

So we would test for the dll in the GAC?  If we did this, we'd still
have to distribute the dll in the tarball, just not build against it or
install it.

I am not familiar enough with Debian's packaging mechanisms to figure
out how they would prefer things.


More information about the Monodevelop-list mailing list