building library dependencies

From: Liam Routt (caligari_at_[hidden])
Date: 2005-09-26 01:53:46

I have a project with a reasonable number of modules, each of which 
creates its own library. There is a web of dependencies between these 
libraries which has resulted in our having to maintain long library 
strings that ensure that all required libraries are linked in.

I've been thinking that there should be a way to use to jam to capture 
this dependency information and create the required list of libraries 
for me.

In a nutshell I've been considering a rule that captures the dependency 
information:

rule LibraryRequires {...}

This rule would simply collect a list of needed libaries into a variable 
named something like depend_libname.

I'd like to be able to, then, have a LinkLibraries rule that looks at 
the list of explicity requested libraries and uses the depend_* 
variables to build up a complete list.

Have others already done this sort of thing?

Does it sound feasible?

Take care,

Liam
--
Liam Routt Ph: [phone]
Research Programmer caligari_at_[hidden]
Computer Science, Melbourne University (or liam_at_[hidden])