<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> You are right, in the next versions we will add ability to specify .pc files along with our library descriptors. But ".pc" files does not provide analogues to following sections from our library descriptor: 1) include_paths: The list of directories to be searched for header files needed for compiling of library headers 2) opaque_types: The list of types that should be skipped while checking 3) internal_functions: The list of functions that should be skipped while checking 4) include_preamble: The list of headers that will be included before each analyzed header So information from ".pc" file will be sufficient for running tool, but will not be enough for obtaining best quality compatibility report. Carl Worth wrote: <blockquote cite="mid:1248893915.6217.19.camel@yoom.home.cworth.org" type="cite"> <pre wrap="">On Wed, 2009-07-29 at 20:41 +0400, Andrey Ponomarenko wrote: </pre> <blockquote type="cite"> <pre wrap="">The wiki-page with the latest release of binary compatibility checker is <a class="moz-txt-link-freetext" href="http://ispras.linux-foundation.org/index.php/ABI_compliance_checker">http://ispras.linux-foundation.org/index.php/ABI_compliance_checker</a> </pre> </blockquote> <pre wrap=""> Hi Andrey, Thanks for sharing this tool. I'm glad to see that it is free software. My first thought in looking at it is that the data it requires in an XML file looks very similar to the data that cairo already provides in its cairo.pc pkg-config file. Have you considered making your tool read pkg-config data files directly? That might make it one step easier for people to run. Thanks, -Carl </pre> </blockquote> </body> </html>