[dpdk-dev] [RFC 1/2] doc: clean ABI/API policy guide

Luca Boccassi bluca at debian.org
Thu Dec 20 09:03:53 CET 2018


On Wed, 2018-12-19 at 12:52 +0000, Ferruh Yigit wrote:
> +    Application
> +    \-> LibA.old
> +    \-> LibB.new -> LibA.new
> +
> +That is a conflict which can be avoided by setting
> ``CONFIG_RTE_MAJOR_ABI``.
> +If set, the value of ``CONFIG_RTE_MAJOR_ABI`` overwrites all -
> otherwise per
> +library - versions defined in the libraries ``LIBABIVER``.
> +An example might be ``CONFIG_RTE_MAJOR_ABI=16.11`` which will make
> all libraries
> +``librte<?>.so.16.11`` instead of ``librte<?>.so.<LIBABIVER>``.

This is not related to your reorganisation, but to solve this problem
properly should we start considering ABI bumps as "sticky", so that in
the example above _both_ libA and libB would get an ABI bump?

-- 
Kind regards,
Luca Boccassi


More information about the dev mailing list