On 18.05.25 20:29, David E. Wheeler wrote:
> On May 16, 2025, at 02:42, Mankirat Singh <mankiratsingh1315@gmail.com> wrote:
>
>> I had wrote two blogs for the same discussing about importance of this project and how I plan to work on this at
blog.mankiratsingh.comI’d greatly appreciate any feedback or suggestions.
>
> Anyone have thoughts on Mankirat’s proposal[1] to start with libabigail’s abidiff utility to produce the the raw data
foreach report, and then write Perl code to transform it to a publishable report?
Well, normally (if there are no problematic ABI changes) the report will
be empty. So I wouldn't spend too much time on the formatting. If
there is a violation, you can just show the raw abidiff output inside
<pre> or whatever.
Generally, this looks like the right direction.
As an additional tip, check the Python source code, they are doing
something like that with libabigail as well.
>
> Best,
>
> David
>
> [1]: https://blog.mankiratsingh.com/posts/abi-compliance-reporting-part-2/
>
