[MonoDevelop] Autotools plugin.

Miguel de Icaza miguel at ximian.com
Mon Aug 14 12:28:17 EDT 2006


> So, say you have a project 'MyLibrary' in solution 'MySolution', a
> pkg-config module will be installed with the name
> 'MySolution.MyLibrary'.

Ah, this is a *brilliant* idea!

> One issue I see is an issue with the guidelines for deploying unstable
> libraries: 
> http://www.mono-project.com/Guidelines:Application_Deployment#Libraries_with_Unstable_APIs
> Say I have one library depending on another unstable library, I can use
> 'pkg-config --libs MyLibrary' to get references to it and to all of it's
> dependencies recursively.  Then I use the 'Libraries' variable to copy
> the actual dlls into my working directory.  However, this will only give
> me the dlls I need for the top-level library not the dependencies.  So I
> would need to go in to the pc file and manually check the other packages
> for the Libraries variable.  I would think the Libraries variable should
> behave like --libs.
> Any thoughts?

Am not sur ewhat is this "Libraries" variable, is this the same as the
output for --libs?

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).

More information about the Monodevelop-list mailing list