Dependencies, their tracking and what we need to improve.

[Auke Kok]

On 07/14/2011 09:44 AM, Duncan Gibson wrote:
>
>> But the problem is this; there are many modules with their configure
>> and cmake scripts that have no corresponding on/off switch.
>> For example; kdelibs4 has no way to enable/disable grantlee even though
>> it can be used during its build. So what is an acceptable method of
>> handling these types of optional_depends?
>
> At one point I wondered whether it would be possible for the "post install"
> phase to run 'lvu links' and add missing modules to the depends cache.
>
> The disadvantage is that it only works for "compiled" modules that access
> installed libraries, and not for modules using Python, Perl, etc., so how
> would lunar know when to call 'lvu links' and when to rely on DEPENDS only?

unfortunately, you can't use `lvu links` as a dependency check, since it 
can go berserk and include everything in he entire world.

just run `lvu links gcc`.

A better approach would be for instance to 'trap' pkg-config stuff. I 
wrote a plugin that monitors it once, and it just shows you a nice list 
of pkg-config files that were referred to once the compilation ends.

We could do something with that, but, it'll be pretty complex to really 
make it useful.

see attachments, go and try it out if you care - needs more work though, 
but a good indicator of what we could do with this.

Auke
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: build-pkg-config.plugin
URL: <http://foo-projects.org/pipermail/lunar-dev/attachments/20110714/92dc0e73/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lunar-pkg-config
URL: <http://foo-projects.org/pipermail/lunar-dev/attachments/20110714/92dc0e73/attachment-0001.ksh>