Sorry for the slow replies. On 4 November 2010 17:41, Vladimir Prus <vladimir@codesourcery.com> wrote:
Maybe. For example, it's always possible to make Jamfile present for all libraries, right at libs/somelib, and report some metatadata.
We'd probably also need metadata in sub-directories.
Library name and short description is a metadata that a build system can make good use of -- say, .pc files as used by pkg-config can have that.
OK, is this something you'd be willing to do, because I wouldn't know how to do it in boost build. It could possibly produce a text file containing the data in an easy to use format (such as json or xml?), or I suppose with the python port it could just create a nested dict. There's no rush, I could create a ticket for later? Daniel