Bug 19588 - Add a --headers-dir1 and --headers-dir2 option to abidiff
Summary: Add a --headers-dir1 and --headers-dir2 option to abidiff
Status: RESOLVED FIXED
Alias: None
Product: libabigail
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
: P2 enhancement
Target Milestone: ---
Assignee: Dodji Seketeli
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-09 17:27 UTC by Dodji Seketeli
Modified: 2016-05-24 08:44 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dodji Seketeli 2016-02-09 17:27:08 UTC
There should be --public-headers-dir1 (and --public-header-dir2) option to abidiff to tell the tool where to find the public headers of the libraries to compare.

By knowing where the public headers are, the tool should be able to auto-generate (and use) a suppression specification that suppresses reports about changes touching types functions and variables that are *not* defined in the header files found under the directories specified by --public-headers-dir1 and --public-headers-dir2.
Comment 1 Dodji Seketeli 2016-05-20 07:51:37 UTC
It looks like the final option names are going to be --headers-dir1 and --header-dir2.

Stay tuned.
Comment 2 Dodji Seketeli 2016-05-24 08:44:46 UTC
This enhancement request has been addressed by commit https://sourceware.org/git/?p=libabigail.git;a=commit;h=e19bf5627a6a2720e6f762266d5b993305af4258 in the master branch of the Git repository.

With this commit, specifying the public headers directories of the libraries being comparted with abidiff, using the --hd1 and --hd2 options, makes the tool automatically filter out changes to types that are not defined in said public headers.

This should be available in the 1.0.rc5 release.