[MonoDevelop] Autotools plugin.
scottell.lists at gmail.com
Wed Jul 5 09:05:46 EDT 2006
On Mon, 2006-07-03 at 14:19 -0400, Miguel de Icaza wrote:
> Well, the situation is that I might have a solution that has a number of
> libraries, for example, I could have a non-GUI library (mylib), then a
> GUI library that builds on the other (mylib-gui)
> And I should be able for example to build app that only requires mylib,
> but not mylib-gui.
> Alternatively, I could have a dozen of libraries in my solution, and
> there is really no need for a third-party application to depend on a
> dozen libraries just because we chose to generate .pc files for the
> whole solution instead of .pc files on a per-library basis.
I think a better way to handle this type of situation would be to permit
the creation of pc files for nested solutions.
Say you have solution 'mylib'. This solution contains all the non-gui
projects (dlls). A pc file would be created for these libs. Then,
within this solution, you could create another solution called
'mylib-gui'. This would have all the gui libs, and another pc file
would be created for this solution with 'mylib' in the 'Requires'
This would give you some granularity without unneccessarily polluting
pkgconfig with a pc for each individual dll.
More information about the Monodevelop-list